Pre-Release PR Triage
jamiepine/voicebox
Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.
Drafts, files, supplements and replies to GitHub issues for bugs, feature ideas and project rules, using the target repository's own templates and etiquette.
SKILL.md written in Chinese; this summary is our English description.
Install GitHub Issue Drafting and Replies
$ npx skills add zyycn/codex-proxy-rs --skill cpr-github-issue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install zyycn/codex-proxy-rs cpr-github-issue --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/zyycn/codex-proxy-rs.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/cpr-github-issue .claude/skills/cpr-github-issue && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cpr-github-issue" agent skill from https://github.com/zyycn/codex-proxy-rs/tree/main/.agents/skills/cpr-github-issue into .claude/skills/cpr-github-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cpr-github-issue", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/zyycn/codex-proxy-rs/tree/main/.agents/skills/cpr-github-issueType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add zyycn/codex-proxy-rs --skill cpr-github-issue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install zyycn/codex-proxy-rs cpr-github-issue --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zyycn/codex-proxy-rs.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/cpr-github-issue .agents/skills/cpr-github-issue && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cpr-github-issue" agent skill from https://github.com/zyycn/codex-proxy-rs/tree/main/.agents/skills/cpr-github-issue into .agents/skills/cpr-github-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cpr-github-issue", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add zyycn/codex-proxy-rs --skill cpr-github-issue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install zyycn/codex-proxy-rs cpr-github-issue --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zyycn/codex-proxy-rs.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/cpr-github-issue .cursor/skills/cpr-github-issue && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cpr-github-issue" agent skill from https://github.com/zyycn/codex-proxy-rs/tree/main/.agents/skills/cpr-github-issue into .cursor/skills/cpr-github-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cpr-github-issue", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/zyycn/codex-proxy-rs.git --path .agents/skills/cpr-github-issue--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add zyycn/codex-proxy-rs --skill cpr-github-issue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install zyycn/codex-proxy-rs cpr-github-issue --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zyycn/codex-proxy-rs.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/cpr-github-issue .gemini/skills/cpr-github-issue && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cpr-github-issue" agent skill from https://github.com/zyycn/codex-proxy-rs/tree/main/.agents/skills/cpr-github-issue into .gemini/skills/cpr-github-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cpr-github-issue", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install zyycn/codex-proxy-rs cpr-github-issueInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add zyycn/codex-proxy-rs --skill cpr-github-issue -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/zyycn/codex-proxy-rs.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/cpr-github-issue .github/skills/cpr-github-issue && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cpr-github-issue" agent skill from https://github.com/zyycn/codex-proxy-rs/tree/main/.agents/skills/cpr-github-issue into .github/skills/cpr-github-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cpr-github-issue", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add zyycn/codex-proxy-rs --skill cpr-github-issue -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install zyycn/codex-proxy-rs cpr-github-issue --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zyycn/codex-proxy-rs.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/cpr-github-issue .opencode/skills/cpr-github-issue && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cpr-github-issue" agent skill from https://github.com/zyycn/codex-proxy-rs/tree/main/.agents/skills/cpr-github-issue into .opencode/skills/cpr-github-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cpr-github-issue", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
cpr-github-issue- GitHub stars
- 738
- Token cost
- ~484 tokens
- SKILL.md length
- 68 words
- Files
- 2
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Drafts, files, supplements and replies to GitHub issues for bugs, feature ideas and project rules, using the target repository's own templates and etiquette.
- Drafting a bug report that follows the repository's issue form
- SKILL.md covers 目标与范围, 按需取材, 正文与证据 and 回复口吻, plus 1 more section
- Calls gh
- Replying to an existing issue discussion in the project's tone
What it does
This skill handles issue work for the codex-proxy-rs project, with instructions written in Chinese. It first confirms which repository receives the issue, separating your fork from upstream. Drafting only prepares the text; the issue is published only when you ask to create or submit it, and merely triggering the skill is not authorization to write remotely. For an existing issue it reads the original post and discussion, then updates or appends instead of opening a duplicate.
For a new issue, it reads the repo's contributing section and the matching form, for API problems, general bugs or feature requests, and searches open and closed issues, PRs and release notes to avoid duplicates. Titles state a symptom or wanted behavior and keep the deployed version, observed result, expected result and root-cause guess apart. Logs are trimmed and redacted, attachments need authorization, and unknown facts are marked as unknown, with no placeholder answers or raw YAML submitted.
Replies follow a house tone: first person, polite and indirect, short natural sentences, and only completed checks reported as done. Publishing uses a connector or gh issue create with a body file, after checking the target, required fields, redaction and duplicates. The agent then reads the issue back and returns the link, or hands over the draft with a note that nothing was submitted.
When your agent uses it
- Drafting a bug report that follows the repository's issue form
- Replying to an existing issue discussion in the project's tone
- Adding new findings to an existing issue instead of opening a duplicate
Example prompts
- “Draft a bug report for the proxy dropping requests, but do not submit it yet.”
- “Reply to this issue thread with what I found when I reproduced it.”
- “Add my log findings to the existing issue instead of opening a new one.”
Requirements
- A GitHub connector or the gh CLI with access to the target repository
What it can do on your machine
Read from SKILL.md and the folder at commit f174320. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
GitHub Issue Drafting and Replies loads about 484 tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 68 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from zyycn/codex-proxy-rs at commit f174320, republished under its Apache-2.0 licence (© zyycn). 68 words, ~484 tokens.
Download SKILL.mdSave it as
.claude/skills/cpr-github-issue/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- cpr-github-issue
- description
- 草拟、创建、补充或回复 GitHub Issue，包括缺陷、功能和协作规则反馈；单独排障或修复不自动发布 Issue
Issue 协作
目标与范围
从用户 URL、remote 和上下文确认接收仓库，fork 场景区分自己的仓库与上游
草拟只准备正文，明确创建或提交才发布；已有授权直接执行，自动命中技能本身不授权远程写入
补充已有 Issue 先读原帖和讨论，按授权更新或追加，不重复新建；无法推断的目标或关键事实才向用户补齐
按需取材
- 新建 Issue 时，本仓库只读提交 Issue及本次匹配的一张表单：接口问题、常规问题或功能建议；协作规则提案可用普通 Issue
- 回复时读取原帖、相关讨论与支撑答复的证据，按下方回复口吻组织内容，不套用新建 Issue 的表单
- 其他仓库读取它自己的相关规则与实际模板，长文档先定位标题再截取，不预读全部模板或 CONTRIBUTING
- 搜索同场景 open/closed Issues、相关 PR 和发布记录，区分主分支修复与已发布修复，不凭标题判断重复；没有新证据时返回已有链接，用户仍要求新建则按其要求处理
- 仅当需要额外排查或修改时使用 cpr-dev-guide，提交症状反馈不以找到根因为前提
- 引用上游行为或提出方案时读取问题与方案依据，涉及 Codex 时按参考仓库优先级先查官方 Codex 源码，三方仓库仅作参考；注明适用版本、来源与缺口
正文与证据
标题说明症状或期望行为，区分发生问题的部署版本、实测结果、预期结果与根因假设
功能和规则提案说明场景、缺少的能力及建议结果，无需硬套缺陷复现步骤
YAML 表单按 attributes.label 和字段顺序组织正文，手工核对必填项、选项与确认项，CLI 不会代做表单校验
未知信息如实标明，影响理解或复现的关键事实先补齐，不提交原始 YAML、占位答案或未确认的勾选项
日志和附件仅含定位所需的脱敏片段，不公开凭据、完整配置或请求转储，不擅自修改代理、TUN、证书环境取证
附件须获授权且可访问，本机路径不算附件；labels 和 assignees 仅按模板或用户要求设置，并确认实际存在
Issue 可记录复现、排查和变更经过，不因此向常规文档追加历史；确需改文档时执行文档检查
回复口吻
草拟和发布 Issue 回复时遵守以下约定：
- 用第一人称“我”表达，称呼对方为“佬友”，称呼自然出现即可，不逐句重复，也不用“我们”“本助手”代称自己
- 语气客气、委婉，直接回应对方的具体问题；补充信息或提出不同意见时说明缘由，避免命令式、责备式表达
- 使用自然短句，简单回复用短段，只有并列信息较多时才分点；少用句号，避免客服套话、机械模板和空泛保证
- 只把实际完成的排查、复现和验证写成“我已……”；未确认的事实如实说明，委婉表达也要说清结论、限制和下一步
发布与收尾
使用可用连接器或 gh，不为提交反馈安装工具、修改仓库配置或启用服务
多行正文通过结构化字段或 UTF-8 文件传递，以下变量须先从已确认的目标与正文赋值：
gh issue create --repo "$issue_repo" --title "$issue_title" --body-file "$issue_body_file"发布前核对目标、必填内容、脱敏与重复记录，更新时保留无关原文；不擅自评论、重开或关闭重复 Issue
超时或结果不明确时先查询远端再重试，发布后回读确认并返回链接；仅草拟或发布失败时提供正文并注明未提交
© zyycn, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/cpr-github-issue of zyycn/codex-proxy-rs.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit f174320
Compare with similar skills
GitHub Issue Drafting and Replies next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| GitHub Issue Drafting and Replies this skillzyycn/codex-proxy-rs | 738 | — | ~484 | Automated safety check: Pass | Apache-2.0 | |
| Pre-Release PR Triagejamiepine/voicebox | 57k | — | ~3.1k | Automated safety check: Pass | MIT | |
| WinAppSDK Triage Meeting Prepmicrosoft/WindowsAppSDK | 4.7k | — | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Ouroboros Maintainer TriageQ00/ouroboros | 6.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| RTK Issue Triagertk-ai/rtk | 83k | — | ~3k | Automated safety check: Notes | Apache-2.0 | |
| Verdaccio Issue Triageverdaccio/verdaccio | 18k | — | ~2.4k | Automated safety check: Pass | MIT |
Similar skills
- Official
WinAppSDK Triage Meeting Prep
microsoft/WindowsAppSDK
Prepares the triage meeting summary for WinAppSDK Needs-Triage issues, with research-backed area suggestions, draft replies and a diff since the last triage.
Ouroboros Maintainer Triage
Q00/ouroboros
Triages and works through GitHub issues and pull requests in the Q00/ouroboros repo as a maintainer, within a stated review boundary and clear limits on what it may change.
RTK Issue Triage
rtk-ai/rtk
Audits open GitHub issues, categorizes them, flags duplicates and linked PRs in three phases, with optional deep analysis and comments posted only after validation.
Verdaccio Issue Triage
verdaccio/verdaccio
Triages an incoming verdaccio/verdaccio issue against the code, the affected release line and related issues, and picks labels from the repository's existing taxonomy.
Issue Triage Loop
cobusgreyling/loop-engineering
Scans open GitHub issues and discussions, flags duplicates, scores priority and proposes labels into issue-triage-state.md without ever labeling or closing.
More from zyycn/codex-proxy-rs
Codex Proxy RS Development Guide
zyycn/codex-proxy-rs
Routes development, troubleshooting, review and documentation tasks on the Codex Proxy RS repository to the right section of its docs, instead of loading the whole architecture or contributing guide.
GitHub PR Workflow for codex-proxy-rs
zyycn/codex-proxy-rs
Prepares, creates, updates and reviews GitHub PRs for the codex-proxy-rs repository, including replying to discussions, with a mode-based reading flow and a fixed reply tone.
Codex Proxy RS Gateway Plugin Development
zyycn/codex-proxy-rs
Guides building, debugging or packaging a standalone gateway plugin for Codex Proxy RS, kept separate from the host runtime, installer or any Vue frontend plugin work.
Codex Proxy RS Release
zyycn/codex-proxy-rs
Plans versions, writes release notes, publishes stable or pre-release builds and recovers from failed releases for Codex Proxy RS, without covering deploys or tag cleanup.
Related
Works with
Categories
Questions about GitHub Issue Drafting and Replies
What does GitHub Issue Drafting and Replies do?
Drafts, files, supplements and replies to GitHub issues for bugs, feature ideas and project rules, using the target repository's own templates and etiquette. This skill handles issue work for the codex-proxy-rs project, with instructions written in Chinese. It first confirms which repository receives the issue, separating your fork from upstream.
When should I use GitHub Issue Drafting and Replies?
GitHub Issue Drafting and Replies fits situations like: drafting a bug report that follows the repository's issue form; replying to an existing issue discussion in the project's tone; adding new findings to an existing issue instead of opening a duplicate.
How do I install GitHub Issue Drafting and Replies in Claude Code?
Run `npx skills add zyycn/codex-proxy-rs --skill cpr-github-issue -a claude-code`. Or copy the skill folder (.agents/skills/cpr-github-issue in zyycn/codex-proxy-rs) into .claude/skills/cpr-github-issue in your project. Claude Code loads it when a task matches its description.
How do I install GitHub Issue Drafting and Replies in Codex?
Run `npx skills add zyycn/codex-proxy-rs --skill cpr-github-issue -a codex`. Or copy the skill folder (.agents/skills/cpr-github-issue in zyycn/codex-proxy-rs) into .agents/skills/cpr-github-issue in your project. Codex loads it when a task matches its description.
Can I use GitHub Issue Drafting and Replies in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add zyycn/codex-proxy-rs --skill cpr-github-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cpr-github-issue, .gemini/skills/cpr-github-issue, .github/skills/cpr-github-issue and .opencode/skills/cpr-github-issue in your project.
What does GitHub Issue Drafting and Replies need to run?
Going by SKILL.md and its folder, GitHub Issue Drafting and Replies needs the command-line tools its instructions call (gh). Our summary lists: A GitHub connector or the gh CLI with access to the target repository.
Does GitHub Issue Drafting and Replies access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is GitHub Issue Drafting and Replies safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does GitHub Issue Drafting and Replies use?
GitHub Issue Drafting and Replies is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does GitHub Issue Drafting and Replies use?
About 484 tokens (SKILL.md is roughly 1.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to GitHub Issue Drafting and Replies?
Skills that share tags, products or a category with GitHub Issue Drafting and Replies: Pre-Release PR Triage (jamiepine/voicebox, 57k stars), WinAppSDK Triage Meeting Prep (microsoft/WindowsAppSDK, 4.7k stars), Ouroboros Maintainer Triage (Q00/ouroboros, 6.2k stars) and RTK Issue Triage (rtk-ai/rtk, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains GitHub Issue Drafting and Replies?
zyycn (a GitHub user) maintains it in zyycn/codex-proxy-rs, which has 738 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 6, 2026.
Source: zyycn/codex-proxy-rs on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.