fix-issue
A workflow for developers to fix GitHub issues. It reads the issue, implements a fix, runs tests, and commits with the proper reference.
Install
mkdir -p .claude/skills/fix-issue-bettercallzaal && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12073" && unzip -o skill.zip -d .claude/skills/fix-issue-bettercallzaal && rm skill.zipInstalls to .claude/skills/fix-issue-bettercallzaal
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when fixing a GitHub issue — reads the issue, implements the fix, writes tests, and commits referencing the issue numberKey capabilities
- →Read GitHub issue details and comments
- →Identify the root cause of an issue
- →Propose a fix approach to the user
- →Implement fixes following ZAO OS conventions
- →Write tests and verify Zod schemas
How it works
The skill reads a GitHub issue, plans a fix, implements it following conventions, runs tests, and creates a commit message referencing the issue number.
Inputs & outputs
When to use fix-issue
- →Fixing reported bugs
- →Implementing small feature requests
- →Patching regressions
About this skill
Fix Issue — GitHub Issue to Commit
End-to-end workflow for fixing a GitHub issue.
Usage
/fix-issue 42
Workflow
1. Read the Issue
Issue details: !`gh issue view $ARGUMENTS`
Issue comments: !`gh issue view $ARGUMENTS --comments`
2. Understand & Plan
- Read all referenced files
- Identify root cause
- Propose fix approach to the user before implementing
3. Implement
- Follow ZAO OS conventions (Zod validation, session checks, Tailwind dark theme, mobile-first)
- Make minimal changes — fix the issue, don't refactor surrounding code
4. Test
- Run
npm run lintandnpm run buildto verify no regressions - If test files exist nearby, run them with
npx vitest run [file] - If the fix touches an API route, verify the Zod schema covers the change
5. Commit
- Stage only the files you changed
- Commit message format:
fix(feature): description (closes #$ARGUMENTS)
Rules
- Always read the full issue + comments before starting
- Always propose the fix approach before implementing
- Never push — let the user decide when to push
- Reference the issue number in the commit message
When not to use it
- →When the user wants to push changes directly without review
- →When refactoring surrounding code beyond the immediate fix
- →When the issue is not a GitHub issue
Limitations
- →Requires reading the full issue and comments before starting
- →Always proposes the fix approach before implementing
- →Never pushes changes; the user decides when to push
How it compares
This skill provides a structured, end-to-end workflow for fixing GitHub issues, including planning, implementation, testing, and committing with specific conventions, unlike a generic code modification process.
Compared to similar skills
fix-issue side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| fix-issue (this skill) | 0 | 4mo | Review | Intermediate |
| dependency-upgrade | 26 | 5mo | Review | Intermediate |
| vitest | 41 | 6mo | No flags | Intermediate |
| testing-workflow | 16 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
vitest
antfu
Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.
testing-workflow
amo-tech-ai
Comprehensive testing workflow for E2E, integration, and unit tests. Use when testing applications layer-by-layer, validating user journeys, or running test suites.
run-nx-generator
nrwl
Run Nx generators with prioritization for workspace-plugin generators. Use this when generating code, scaffolding new features, or automating repetitive tasks in the monorepo.
zod-4
prowler-cloud
Zod 4 schema validation patterns. Trigger: When creating or updating Zod v4 schemas for validation/parsing (forms, request payloads, adapters), including v3 -> v4 migration patterns.
write-unit-tests
tldraw
Writing unit and integration tests for the tldraw SDK. Use when creating new tests, adding test coverage, or fixing failing tests in packages/editor or packages/tldraw. Covers Vitest patterns, TestEditor usage, and test file organization.