Read a GitHub Issue, and implement the code after plan confirmation.
Flow
Step 1: Get the Issue
Get the content from the Issue URL or number:
gh issue view <url-or-number>
Step 2: Investigate the codebase and create an implementation plan
Investigate related code based on the Issue content, andlocal-plans/ create a detailed plan file in
2-1. Investigate related code
Investigate the following in parallel:
- Current state of files to be changed (Glob / Grep / Read)
- Reusable existing components and utilities
- Relevant API endpoints
- Similar implementation patterns
2-2. Save the plan file to local-plans/ save to
File name: <issue-number>-<issue-slug>.md(e.g.: local-plans/42-add-auth.md)
Required sections of the plan:
# [Issue タイトル]
## Context
Issue の背景・目的・なぜこの変更が必要か。
## Approach
実装方針。選択肢がある場合は採用理由も記述。
## File Changes
| ファイルパス | 変更内容 |
|-------------|---------|
| `src/...` | 〜を追加 |
| `lib/...` | 〜を修正 |
## Reuse
再利用する既存実装のパスと用途。
## Test Plan
- [ ] 動作確認手順
- [ ] エッジケース確認
Step 3: Present the plan to the user and wait for approval
Display the contents of the created plan file, and start implementation only after obtaining the user's approval. Do not start implementation without approval.
Step 4: Implement the code
Implement according to CLAUDE.md and project conventions.
For extensive changes, use isolation: "worktree" to carry it out safely.
Step 5: Security review (required)
Perform a security check with the Agent tool.
Check items:
- OWASP Top 10
- Hardcoding of API keys and secrets
- Input validation
- Possibility of XSS
If any issues are found, fix them before proceeding to the next step.
Step 6: Run tests
Run the project's test command. If tests fail, fix them.
Step 7: Create a commit
create-commit Use the skill to create a commit in Conventional Commits format.
Notes
- Do not start implementation without the user's approval
- Do not commit while security issues remain unresolved
- Commit large changes in separate steps