Automated summary
This skill automates the end-to-end fix of a GitHub issue, from reading the ticket through committing a change that references its number.
Strengths
- Runs the whole pipeline: reads the issue and its comments with gh, analyses, implements, tests, then commits.
- Requires the agent to propose a fix approach to the user before touching any code.
- Enforces a tight scope — fix the issue, no refactoring of surrounding code.
- Checks for regressions with npm run lint, npm run build, and vitest on the affected test files.
Limitations
- Assumes the gh CLI is installed and authenticated and that the repo defines npm lint and build scripts.
- The baked-in conventions (Zod validation, session checks, Tailwind dark theme, mobile-first) are specific to ZAO OS and won't fit arbitrary projects.
- Never pushes, so opening the PR and running CI stay manual steps.
Use it when you have a GitHub issue number and want a guided, tested fix committed with a closing reference to that issue.
Skip it for repos that don't follow the ZAO OS stack and conventions, or when the gh CLI isn't available in the environment.
Security analysis
CautionThe skill instructs running gh issue view with a user-supplied argument and then npm/npx commands. These are legitimate for the task but involve shell execution without declared tool permissions, creating a moderate risk if arguments are not sanitized.
- •Executes shell commands (gh, npm, npx) without declaring allowed-tools, which could lead to command injection if the issue number argument contains shell metacharacters.
- •Uses the GitHub CLI to fetch issue details and run build/test commands, which is legitimate but requires caution.
Examples
/fix-issue 42/fix-issue 137 — the signup form throws a Zod validation error when the email field is left empty/fix-issue 208 — the profile card overflows horizontally on narrow screens in the dark themename: fix-issue description: Use when fixing a GitHub issue — reads the issue, implements the fix, writes tests, and commits referencing the issue number disable-model-invocation: true argument-hint: "[issue-number]"
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
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/fix-github-issue-mryiqim7/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/fix-github-issue-mryiqim7' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/fix-github-issue-mryiqim7/download' --output '.skill-downloads/fix-github-issue-mryiqim7/SKILL.md.part' && mv '.skill-downloads/fix-github-issue-mryiqim7/SKILL.md.part' '.skill-downloads/fix-github-issue-mryiqim7/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/fix-github-issue-mryiqim7/SKILL.md' && test -s '.skill-downloads/fix-github-issue-mryiqim7/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/fix-issue' && cp -R '.skill-downloads/fix-github-issue-mryiqim7' '.claude/skills/fix-issue'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/fix-github-issue-mryiqim7'openskills read 'fix-github-issue-mryiqim7'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/fix-github-issue-mryiqim7/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.