메뉴
Fix a GitHub issue end-to-end. Use when given an issue number to fix, implementing bug fixes, or addressing reported problems.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | fix-issue |
| description | Fix a GitHub issue end-to-end. Use when given an issue number to fix, implementing bug fixes, or addressing reported problems. |
A complete workflow for fixing GitHub issues from understanding the problem to creating a pull request.
$ARGUMENTS: GitHub issue number (e.g., 123 or #123)gh issue view $ARGUMENTS
Analyze:
Search for relevant code:
# Search for keywords from the issue
grep -r "keyword" src/
# Find related files
find . -name "*.ts" | xargs grep -l "relatedTerm"
Understand:
git checkout -b fix/issue-$ARGUMENTS-<brief-description>
Apply the minimum necessary change to resolve the issue:
Create tests that:
Run the verification cycle:
pnpm lint
pnpm test
pnpm build
Or invoke the verifier subagent for comprehensive validation.
git add <specific-files>
git commit -m "fix(scope): brief description
Fixes #$ARGUMENTS"
git push -u origin HEAD
gh pr create --title "fix(scope): description" --body "$(cat <<'EOF'
## Summary
Fixes #$ARGUMENTS
## Problem
[Description of the issue]
## Solution
[How this PR fixes it]
## Testing
- [ ] Added test case for the bug
- [ ] All tests pass
- [ ] Manually verified the fix
## Changes
- [List specific changes]
EOF
)"
| Task | Command |
|---|---|
| View issue | gh issue view <number> |
| List issues | gh issue list |
| Create branch | git checkout -b fix/issue-<n>-<desc> |
| Link PR to issue | Include Fixes #<n> in commit message |
| Close issue via PR | Include Closes #<n> in PR body |
Consistently bump and synchronize versions across all packages in the monorepo using pnpm. Use this to ensure the root and all workspace packages share the same version number.
Run comprehensive integration tests using real skills (Vercel, Anthropic, Expo) in a Docker container. Managed via Makefile for standard lifecycle control.
Synchronize technical sections in README.md and CONTRIBUTING.md with the actual project state.
Run linters and fix violations, formatting errors, or style mismatches using Trunk. Use when code quality checks fail, before submitting PRs, or to repair "broken" linting states.
Build the project and automatically fix any build errors, compilation failures, or type mismatches. Use when the project fails to build, shows "broken" states, or after making significant changes.
Perform a "hard reset" of the development environment. Use when dependencies are corrupted, lockfiles are out of sync, or environment tools (Trunk/pnpm) are in an inconsistent state.