fix-issue

SkillDev tools

Analyze and fix a GitHub issue end-to-end, producing a PR

Available today. Use it from your connected AI after setup.

No other account needed.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the fix-issue skill

What this skill tells your AI

The instructions your AI receives, as published by vavallee/bindery in .claude/skills/fix-issue/SKILL.md and read by ahel’s review.

Fix GitHub issue $ARGUMENTS.

gh issue view <n> — read the issue and all comments. If reproduction steps are missing, say so and draft a comment asking for them (tone rules in CLAUDE.local.md) instead of guessing.
Search the codebase for the affected area; read before writing.
Write a failing test that reproduces the bug first. No test = no fix.
Implement the fix on a branch fix/<n>-<slug>. Address the root cause, not the symptom.
Security-sensitive area (auth, settings endpoints, user-scoped resources, proxy headers)? Check against the conventions in CLAUDE.md before proceeding.
Run the affected package tests, then lint. Fix what breaks.
Add a fragment under changelog.d/ (format in changelog.d/README.md; preview with make changelog). Do not edit CHANGELOG.md directly — a maintainer assembles it at release time.
Push, open a PR targeting main with Fixes #<n>, summarize the root cause in the body.

Never tag a release from this workflow — releases follow the flow in CLAUDE.md and are Vincent's call.

Advanced