Fix Issue
End-to-end GitHub issue resolver — fetch, classify, branch, fix with TDD, Codex audit loop, test gate, docs-sync, version bump, PR, and post-merge close-gate finalizer. Use this skill whenever the user wants to fix a bug from a GH issue, asks 'fix issue #N', 'fix bug 115', 'work on issues #123 #456 #789', 'resolve this GH bug', or pastes a GH issue URL/number for resolution. Also handles `question`-labeled issues (inline answer + comment, no branch). REDIRECTS feature/enhancement issues to feature-workflow per rule 47. Supports both single-issue and multi-issue (worktree) pipelines.
Install
npx skills add lllyys/vreader --skill fix-issuegit clone --depth 1 https://github.com/lllyys/vreader.git /tmp/vreader
mkdir -p ~/.claude/skills
cp -r /tmp/vreader/.claude/skills/fix-issue ~/.claude/skills/fix-issuePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Fix Issue Resolve one or more GitHub issues end-to-end: fetch, classify, branch, fix with TDD, Codex audit loop, test gate, docs-sync, version bump, PR, and post-merge close-gate finalizer. ## Input ```text $ARGUMENTS ``` ## Scope | Issue type | Path inside this skill | |---|---| | Bug (label `bug` or body describes broken behavior) | Single-issue **Bug Pipeline** below | | Question (label `question`) | Inline answer + comment, no branch/PR | | Feature / enhancement | **REDIRECT** to `/feature-workflow` (see "Feature handling" below) | | Multiple issues at once | **Multi-Issue Pipeline** (one worktree per issue) | ### Feature handling — read this before fixing a feature here `.claude/rules/47-feature-workflow.md` is **binding for every feature implementation**: Plan → Independent plan audit → TDD → Implementation audit → Device/integration verification → Merge. Six gates, never skip one. This skill cannot run Gate 2 (independent plan audit by a separate agent context) or Gate 5 (device/integration verification + evidence file) inline. Therefore: **Always redirect features to `/feature-workflow`. STOP this pipeline.** No user waiver bypasses Gates 2 or 5 — rule 47 is binding for every feature regardless of size. The old escape hatch (10+ files / 4+ work items) is gone; the previous "opt out in writing" is gone too. The skill's old `3b. Feature Path` is removed. Feature handling lives entirely in `/feature-workflow`. ## Hooks you'll trip
Details
- Skill name
fix-issue- Repository
- lllyys/vreader
- Path
.claude/skills/fix-issue/SKILL.md- Repo updated
- 6 August 2026
FAQ
What does the Fix Issue skill do?
End-to-end GitHub issue resolver — fetch, classify, branch, fix with TDD, Codex audit loop, test gate, docs-sync, version bump, PR, and post-merge close-gate finalizer. Use this skill whenever the user wants to fix a bug from a GH issue, asks 'fix issue #N', 'fix bug 115', 'work on issues #123 #456 #789', 'resolve this GH bug', or pastes a GH issue URL/number for resolution. Also handles `question`-labeled issues (inline answer + comment, no branch). REDIRECTS feature/enhancement issues to feature-workflow per rule 47. Supports both single-issue and multi-issue (worktree) pipelines.
How do I install the Fix Issue skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add lllyys/vreader --skill fix-issue. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Fix Issue popular?
It lives in lllyys/vreader, which has 49 GitHub stars and 21 forks.
Related skills
AI Coding Agents
49lllyys/vreader
Comprehensive guide for using Codex CLI (OpenAI) and Claude Code CLI (Anthropic) - AI-powered coding agents. Use when orchestrating CLI commands, automating tasks, configuring agents, or troubleshooting issues.
Dispatch
49lllyys/vreader
Parallel lane dispatch — the ONLY sanctioned multi-item fan-out (feature #130, rule 55). Use when the user asks to fix several bugs at once ('fix #a #b #c'), implement independent feature WIs in parallel, or run a dispatch batch. Orchestrates worktree-isolated implementer lanes on leased simulators, validates HANDOFFs, and runs the serial integration tail (rebase → re-test → tracker/docs → version-at-slot → PR → merge-from-worktree → tag). A single item degrades to the inline /fix-issue or /feature-workflow flow.
Feature Workflow
49lllyys/vreader
Run the binding 6-gate feature workflow end-to-end per rule 47 (Plan → Independent Plan Audit → TDD Implementation → Implementation Audit Loop → Device/Integration Verification → Merge). Use this skill whenever the user wants to implement a new feature in vreader, asks 'implement feature #N', 'work on feature 47', 'start the feature workflow', 'plan + build feature X', or describes building a new capability that doesn't yet exist. NOT for fixing broken implementations (that's fix-issue). The skill drives the row from `TODO` → `VERIFIED` through six gates that must never be skipped — author/aud
Hallucinatory Terrain
113Hmbown/Wizards-of-the-Ghosts
In D&D, Hallucinatory Terrain makes natural terrain look like a different kind of terrain — a field appears as a forest, a hill appears as a valley. The underlying terrain is unchanged; only the perception shifts. The real-world version is environment staging: test environments styled to look like production, sandbox databases seeded with realistic data, training simulations that overlay a learning scenario onto real infrastructure. Hallucinatory Terrain does not change the real system. It changes how the system appears so you can test, train, or demo safely.
Design Distiller
65Yrzhe/claude-skills
Scrape any website's design system into a structured Design MD + decomposed design tokens. Supports Browser Use Cloud, Playwright, Chrome headless, source code analysis. Maintains a Reference Pool of full Design MDs and a Digest Pool of cross-site design tokens for mix-and-match composition.
Mirage Arcane
113Hmbown/Wizards-of-the-Ghosts
In D&D, Mirage Arcane goes beyond Hallucinatory Terrain — the illusory terrain actually has substance. You can walk on illusory bridges, feel illusory walls. The real-world version is the deep simulation: digital twins, high-fidelity synthetic environments, test harnesses so realistic that systems under test cannot distinguish them from production. Mirage Arcane is the most dangerous illusion because its power is in being indistinguishable from reality. That same power makes it the most useful for stress testing, training, and scenario planning — but it requires the strongest labeling discipli
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.