Invoke this skill when the user asks to implement, take, pick up, work on, tackle, start, or grab a GitHub issue. Triggers on phrases like "implement issue #N", "take issue #N", "work on #N", "do #N", or "pick up issue #N". Handles the full workflow from reading the issue through opening a pull request.
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Implement Github Issue?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/brandonavant-implement-github-issue)
---
name: implement-github-issue
description: Invoke this skill when the user asks to implement, take, pick up, work on, tackle, start, or grab a GitHub issue. Triggers on phrases like "implement issue #N", "take issue #N", "work on #N", "do #N", or "pick up issue #N". Handles the full workflow from reading the issue through opening a pull request.
argument-hint: [ issue-number-or-url ]
allowed-tools: Bash(git *), Bash(gh *)
---
# Implement GitHub Issue
Follow this workflow exactly, in order. Do not skip steps.
## Step 1 — Read the Issue
Fetch the issue details:
```
gh issue view $ARGUMENTS --json number,title,body,labels
```
Parse the response. You need:
- **number**: The issue number
- **title**: The issue title
- **body**: The full issue body — these are your requirements
- **labels**: Any labels (used to infer the branch prefix in Step 4)
If the issue cannot be found, stop and tell the user.
## Step 2 — Ensure Clean Working Tree
Run `git status --porcelain`. If there is any output, **stop** and tell the user:
> Your working tree has uncommitted changes. Please commit or stash them before implementing a new issue.
Do not proceed until the working tree is clean.
## Step 3 — Checkout and Pull Main
Determine the default branch name, then checkout and pull:
```
git checkout main && git pull
```
If this fails (e.g., merge conflicts), stop and tell the user.
## Step 4 — Cut a New Branch
Derive a branch name using this convention:
1. **Prefix** — infer from issue labels or title keywords:
- `bug` or `fix` label, or title contains "fix"/"bug" → `fix/`
- `enhancement` or `feature` label, or title suggests new capability → `feat/`
- `docs` or `documentation` label → `docs/`
- `refactor` label → `refactor/`
- `audit` label or title contains "audit" → `audit/`
- Fallback → `feat/`
2. **Slug** — lowercase the issue title, replace non-alphanumeric characters with hyphens,
collapse consecutive hyphens, trim leading/trailing hyphens, truncate to 50 characters.
3. **Suffix** — append the issue number.
Format: `<prefix><slug>-<number>`
Example: Issue #42 titled "Add widget component" with label `enhancement` →
`feat/add-widget-component-42`
```
git checkout -b <branch-name>
```
## Step 5 — Implement the Issue
Using the issue body as your requirements, implement the necessary changes.
- Read relevant existing code before modifying anything.
- Follow all project conventions defined in CLAUDE.md and any applicable rules.
- Make the minimum changes necessary to satisfy the issue requirements.
- If the issue is unclear or ambiguous, ask the user for clarification before proceeding.
## Step 6 — Commit, Push, and Open a PR
Once the implementation is complete:
1. **Stage** the relevant changed files by name (prefer explicit paths over `git add -A`).
2. **Commit** with a message referencing the issue. Use this format:
```
<type>: <short description> (closes #<number>)
```
3. **Push** the branch:
```
git push -u origin <branch-name>
```
4. **Create a PR** using the `create-github-pr` skill (`.claude/skills/create-github-pr/SKILL.md`).
Follow that skill's full workflow (write body to temp file, create with `--body-file`, validate,
clean up). The PR title should match the commit message (without the `closes` suffix). The body
must include:
```
## Summary
<1-3 bullet points summarizing the changes>
Closes #<number>
## Test plan
<Bulleted checklist of how to verify the changes>
🤖 Generated with [Claude Code](https://claude.com/claude-code)
```
5. **Report** the PR URL to the user.