Pre-Release PR Triage
jamiepine/voicebox
Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.
Fix a GitHub issue end-to-end — fetches issue, creates worktree, plans and implements fix, runs validation, opens PR, cleans up.
Install Fix
$ npx skills add exercism/website --skill fix -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install exercism/website fix --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/exercism/website.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/fix .claude/skills/fix && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "fix" agent skill from https://github.com/exercism/website/tree/main/.claude/skills/fix into .claude/skills/fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/exercism/website/tree/main/.claude/skills/fixType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add exercism/website --skill fix -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install exercism/website fix --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/exercism/website.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/fix .agents/skills/fix && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "fix" agent skill from https://github.com/exercism/website/tree/main/.claude/skills/fix into .agents/skills/fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add exercism/website --skill fix -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install exercism/website fix --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/exercism/website.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/fix .cursor/skills/fix && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "fix" agent skill from https://github.com/exercism/website/tree/main/.claude/skills/fix into .cursor/skills/fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/exercism/website.git --path .claude/skills/fix--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add exercism/website --skill fix -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install exercism/website fix --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/exercism/website.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/fix .gemini/skills/fix && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "fix" agent skill from https://github.com/exercism/website/tree/main/.claude/skills/fix into .gemini/skills/fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install exercism/website fixInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add exercism/website --skill fix -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/exercism/website.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/fix .github/skills/fix && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "fix" agent skill from https://github.com/exercism/website/tree/main/.claude/skills/fix into .github/skills/fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add exercism/website --skill fix -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install exercism/website fix --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/exercism/website.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/fix .opencode/skills/fix && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "fix" agent skill from https://github.com/exercism/website/tree/main/.claude/skills/fix into .opencode/skills/fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
fix- GitHub stars
- 550
- Token cost
- ~1.2k tokens
- SKILL.md length
- 576 words
- Files
- 1
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Fix a GitHub issue end-to-end — fetches issue, creates worktree, plans and implements fix, runs validation, opens PR, cleans up.
- Works in 8 steps: Understand the issue → Plan the fix → Create a worktree → …
- Tasks that involve Git worktrees
- SKILL.md covers Issue details, Critical: Two phase. and Workflow
- Calls git, gh and yarn; reaches claude.com
What it does
Fix is an agent skill from exercism/website. Fix a GitHub issue end-to-end — fetches issue, creates worktree, plans and implements fix, runs validation, opens PR, cleans up.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Git worktrees. It works with GitHub and Git. The repository describes itself as: The codebase for Exercism's website. The licence is AGPL-3.0.
When your agent uses it
- Tasks that involve Git worktrees
Example prompts
- “/fix”
Requirements
- Pre-approved tools (allowed-tools): Bash, Read, Write, Edit, Glob, Grep, WebFetch, WebSearch
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 6cb5042. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
BashReadWriteEditGlobGrepWebFetchWebSearch
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitghyarnbundle
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
claude.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Fix loads about 1.2k tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 576 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Bash, Read, Write, Edit, Glob, Grep, WebFetch, WebSearch
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from exercism/website at commit 6cb5042, republished under its AGPL-3.0 licence (© exercism). 576 words, ~1,218 tokens.
Download SKILL.mdSave it as
.claude/skills/fix/SKILL.md (or your agent's skills folder).- name
- fix
- description
- Fix a GitHub issue end-to-end — fetches issue, creates worktree, plans and implements fix, runs validation, opens PR, cleans up.
- allowed-tools
- Bash, Read, Write, Edit, Glob, Grep, WebFetch, WebSearch
- argument-hint
- issue-number-or-url
- disable-model-invocation
- true
Fix GitHub Issue
You are fixing a GitHub issue for the exercism/website repository.
Issue details
!`gh issue view $(echo "$ARGUMENTS" | grep -oE '[0-9]+$') --json number,title,body,labels,comments`Issue number: !echo "$ARGUMENTS" | grep -oE '[0-9]+$'
Critical: Two phase.
Your work is split into two phases.
The first phase is purely planning. You must NOT make any changes to git state (switching branches, creating branches, creating worktrees, etc). You should presume that other work is SIMULTANEOUSLY happening WHILE you are planning.
Once the plan has been APPROVED by the user you should check the current git state:
- Run
git statusto check for uncommitted changes. - If there are uncommitted or staged changes, STOP and ask the user how to proceed. Do NOT stash or discard anything.
Never destroy or discard existing work.
If the plan has been approved and the working tree is clean, continue with your work.
Workflow
Follow these steps in order. Do not skip any step.
Step 1: Understand the issue
Read the issue details above carefully. Identify:
- What is broken or needs to change
- Which parts of the codebase are likely affected
- Any reproduction steps or error messages mentioned
Read the relevant docs/context/ files for the area of the codebase involved.
Step 2: Plan the fix
Do NOT create a branch or worktree yet. Stay on the current branch while planning.
Use /plan to enter plan mode. Explore the codebase thoroughly:
- Find the relevant files using Glob and Grep
- Read the code to understand current behavior
- Identify what needs to change and why
- Check for existing test coverage
- Look at similar patterns in the codebase for reference
Design a complete fix before writing any code.
Step 3: Create a worktree
Only create the worktree after the plan is approved. The issue number has been extracted above (works whether the argument was a full URL like https://github.com/exercism/website/issues/8370 or just 8370).
git pull --ff-only origin main
mkdir -p worktrees
git worktree add worktrees/fix-<issue-number> -b fix/<issue-number>
cd worktrees/fix-<issue-number>After creating the worktree, symlink node_modules and husky from the main repo so that JS tooling (prettier, eslint, jest) and pre-commit hooks work without a full yarn install:
ln -s /Users/iHiD/Code/exercism/website/node_modules node_modules
ln -s /Users/iHiD/Code/exercism/website/.husky/_ .husky/_CRITICAL: You MUST cd into the worktree immediately after creating it. All subsequent work — file reads, edits, bash commands, tests — MUST happen from inside the worktree directory using cd worktrees/fix-<issue-number> && <command> on every Bash call. Do NOT use absolute paths to the worktree from the main repo. The main repo stays untouched on its current branch.
Show full SKILL.md (193 more words)Show less
Step 4: Implement the fix
After the plan is approved and the worktree is created, implement the changes:
- Follow existing patterns and conventions in the codebase
- Business logic belongs in
/app/commands/using the Mandate pattern - Keep controllers thin — delegate to commands
- Add or update tests as appropriate (Minitest, FactoryBot)
- Keep changes minimal and focused on the issue
Step 5: Run tests
Run the relevant tests for the changes you made:
bundle exec rails test <test-file-or-directory>If you made front-end changes, also run yarn test before committing.
Rubocop and brakeman will be checked automatically by the pre-commit hook when you commit — you do not need to run them manually.
Step 6: Commit the changes
Stage only the files you changed (do not use git add -A or git add .). Write a clear commit message that describes the fix.
Step 7: Push and create a PR
Push the branch and create a pull request:
git push -u origin fix/<issue-number>Create the PR using gh pr create. The PR body must include Closes #<issue-number> to auto-close the issue on merge:
gh pr create --title "<concise title>" --body "$(cat <<'EOF'
Closes #<issue-number>
## Summary
<bullet points describing what changed and why>
## Test plan
<checklist of how the fix was validated>
🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"Step 8: Clean up worktree
cd /Users/iHiD/Code/exercism/website
git worktree remove worktrees/fix-<issue-number>This removes the worktree directory. The branch remains on the remote for the PR.
Report the PR URL to the user.
© exercism, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/fix of exercism/website.
Open the folder on GitHubat commit 6cb5042
Compare with similar skills
Fix next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Fix this skillexercism/website | 550 | — | ~1.2k | Automated safety check: Notes | AGPL-3.0 | |
| Pre-Release PR Triagejamiepine/voicebox | 57k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Ff Worktreesdamus-io/damus | 2.1k | — | ~451 | Automated safety check: Pass | GPL-3.0 | |
| Clean Complete Branchesjtenniswood/espcontrol | 1.1k | — | ~820 | Automated safety check: Pass | Custom licence | |
| Clean Merged Branch Foldersjtenniswood/espcontrol | 1.1k | — | ~813 | Automated safety check: Pass | Custom licence | |
| Kanvibe Release Deployrookedsysc/kanvibe | 143 | — | ~12k | Automated safety check: Notes | AGPL-3.0 |
Similar skills
Ff Worktrees
damus-io/damus
Fast-forward master and every git worktree branch up to a target ref (default github/master), skipping any worktree with unmerged commits.
Clean Complete Branches
jtenniswood/espcontrol
Clean up completed Git branches and worktrees for this repository both locally and on GitHub.
Clean Merged Branch Folders
jtenniswood/espcontrol
Clean up local branch worktree folders for this repository after their branches or pull requests have merged to main.
Kanvibe Release Deploy
rookedsysc/kanvibe
A skill your agent uses whenever releasing or deploying KanVibe desktop from a clean, up-to-date dev checkout: ask only for the target version and release-note approval, then let the AI update…
Kc Issue
imran31415/kube-coder
Spin up an isolated agent to work a GitHub issue of kube-coder or any other repo checked out in the workspace.
Related
Categories
Questions about Fix
What does Fix do?
Fix a GitHub issue end-to-end — fetches issue, creates worktree, plans and implements fix, runs validation, opens PR, cleans up. Fix is an agent skill from exercism/website. Fix a GitHub issue end-to-end — fetches issue, creates worktree, plans and implements fix, runs validation, opens PR, cleans up.
When should I use Fix?
Fix fits situations like: tasks that involve Git worktrees.
How do I install Fix in Claude Code?
Run `npx skills add exercism/website --skill fix -a claude-code`. Or copy the skill folder (.claude/skills/fix in exercism/website) into .claude/skills/fix in your project. Claude Code loads it when a task matches its description.
How do I install Fix in Codex?
Run `npx skills add exercism/website --skill fix -a codex`. Or copy the skill folder (.claude/skills/fix in exercism/website) into .agents/skills/fix in your project. Codex loads it when a task matches its description.
Can I use Fix in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add exercism/website --skill fix -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fix, .gemini/skills/fix, .github/skills/fix and .opencode/skills/fix in your project.
What does Fix need to run?
Going by SKILL.md and its folder, Fix needs the command-line tools its instructions call (git, gh, yarn and bundle). Its frontmatter pre-approves these tools: Bash, Read, Write, Edit, Glob, Grep, WebFetch, WebSearch.
Does Fix access the network?
SKILL.md names 1 domain. In commands or code: claude.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Fix safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Fix use?
Fix is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Fix use?
About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Fix?
Skills that share tags, products or a category with Fix: Pre-Release PR Triage (jamiepine/voicebox, 57k stars), Ff Worktrees (damus-io/damus, 2.1k stars), Clean Complete Branches (jtenniswood/espcontrol, 1.1k stars) and Clean Merged Branch Folders (jtenniswood/espcontrol, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Fix?
exercism (a GitHub organization) maintains it in exercism/website, which has 550 GitHub stars. The repository was last updated on October 4, 2026.
Source: exercism/website on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.