メニュー
Investigate and fix a GitHub issue. Use when given an issue number or URL, or when the user says 'fix issue'.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "is this over-engineered", or invokes /prune. Complements correctness-focused review; this one only hunts complexity.
Implement code incrementally with quality gates. Use when the user says 'build', 'implement', or when starting the implementation phase of an approved plan.
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Structured production-incident investigation. Forces evidence-first hypothesis ranking before any code change. Use when given an error message, Sentry alert, failing log, or 'investigate <X>' request.
Fetch and digest Sentry issue data (issue summary, tags, stack trace, breadcrumbs, latest event) by short ID, numeric issue ID, or sentry.io URL. Org-agnostic - works for any Sentry org the local token can access. Use when the user mentions a Sentry issue or short ID (e.g. MY-PROJECT-4X2), pastes a sentry.io issue URL, or asks to investigate/debug a Sentry error.
Create or update a diagram. Picks mermaid vs drawio per rules/diagrams.md, writes the source file, previews via MCP. Use when the user says 'diagram', '/diagram', or asks for a flowchart/architecture/sequence/state diagram.
| name | fix-issue |
| description | Investigate and fix a GitHub issue. Use when given an issue number or URL, or when the user says 'fix issue'. |
Fix the GitHub issue: $ARGUMENTS
Follow this workflow:
why-not-mechanizable: skill workflow guidance; each step requires understanding the issue, the codebase, and the prior state of the work.
gh issue view $ARGUMENTS --json title,body,labels,assignees,comments to get full issue details (review-time: see section note)~/.claude/agents/ (see rules/agent-routing.md). Their guardrails apply throughout the fix. (review-time: see section note).claude/state/research/YYYY-MM-DD-issue-<number>.md. (review-time: see section note)(review-time: see section note)(review-time: see section note).claude/state/plans/YYYY-MM-DD-fix-issue-<number>.md with: (review-time: see section note)
(review-time: see section note)(review-time: see section note)npx tsc --noEmit), lint, and full test suite (hook)fix(scope): description) referencing the issue (hook)gh pr create (hook)