Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/igorrochap/commitgen --skill fix-review명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
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.
SKILL.md 표시 중
| 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