用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/igorrochap/commitgen --skill fix-review命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Mark the current issue as done
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (repo conventions) and Spec (does it match the originating issue/PRD). Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
Apply Uber's Go Style Guide when generating, editing, or reviewing Go code.
| name | fix-review |
| description | Fix problems pointed out in a code review session. |
Fix the problems pointed out in the code review.
The findings are usually given to you directly in the current conversation (e.g. a "Blocking findings" list in the prompt) — work from those first. Only look for a review document if you're explicitly pointed at one; where that document lives depends on how the project tracks reviews (a local .scratch/<project>/reviews/ file, or a GitHub PR/issue comment) — don't assume .scratch.
If there's a suggested order of work, follow it. If not, resolve the most critical findings first and report what you didn't resolve and why.
/refactoring skill is your biggest friend if the findings are only about coding standards