Implement a GitHub issue, optionally from an existing plan
Scanned 9/6/2026
Install to Claude Code
npx -y skills add Jartan-LLC/grimoire --skill implement-issue --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Implement Issue?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/jartan-llc-implement-issue)More formats (shields.io, HTML) on the badges page.
---
name: implement-issue
description: Implement a GitHub issue, optionally from an existing plan
argument-hint: Issue number (may include additional context)
---
# Implement Issue
Implement changes for a GitHub issue.
## Process
### 1. Load Context
Determine the issue number from the user's request, which may carry context beyond the number. Fetch the issue and any plan comments:
```bash
gh issue view <issue-number> --comments
```
Also check `.claude/workspace/` for any plan files related to this issue. If no plan exists for a complex issue, suggest running `/praxis:plan-issue` first.
### 2. Setup Branch
Check existing local and remote branches for one related to this issue -- it may be named by issue number (`feature/issue-123`) or by description (`feature/audit-improvements`). If one exists, check it out. If not, create a new branch. For sub-issues of a larger feature, branch from the parent feature branch rather than main.
### 3. Read Relevant Docs
Based on the issue area, read the appropriate project documentation in `docs/`.
### 4. Implement
Follow the plan if one exists. Work through changes methodically. Make progressive commits as logical units of work are completed rather than one monolithic commit at the end.
### 5. Update Documentation
Changed behavior may need doc updates. Commit doc changes.
### 6. Verify
Run the Verify commands from `CLAUDE.md`. Fix any failures and commit the fixes before pushing.
### 7. Push
Push the branch with all commits.
### 8. Post Summary
```bash
gh issue comment <issue-number> --body "## Implementation Complete
Branch: \`<branch-name>\`
### Changes
- [categorized list of what was added/modified/removed]
### Documentation
- [docs created or updated, or 'No doc changes needed']
---
*Generated by Claude -- reply with \`/praxis:create-pr <issue-number>\` to create a pull request*"
```
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!