Fix Issue

Automated GitHub issue resolution that spins up parallel analysis agents to investigate root cause, search for similar patterns in your codebase and memory MCP, then generates a fix with tests and prevention recommendations. It fetches the issue via gh CLI, scales investigation depth by effort level (quick fix vs full RCA), and can resume mid-flow if interrupted. The task management is mandatory and well-structured, though the docs lean heavy on process. Best for teams that want systematic debugging with traceable reasoning instead of one-off patches. Requires memory and context7 MCP servers plus some setup, but the multi-host support for GitHub Enterprise, GitLab, and Bitbucket is solid if you work across platforms.

skills.sh installs: 217
GitHub stars: 301
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add yonatangross/orchestkit --skill fix-issue --agent claude-code

Installs into .claude/skills of the current project.

Files

Fix Issue

Host-neutral workflow. Invoke by skill name (fix-issue). Claude Code slash routing, YAML hook loaders, and .claude/chain live in references/claude-code.md.

Systematic issue resolution with hypothesis-based root cause analysis, similar issue detection, and prevention recommendations.

Quick Start

fix-issue 123
fix-issue 456

Opus 5.5: Root cause analysis uses native adaptive thinking. Dynamic token budgets scale with context window for thorough investigation.

CC ≥ 2.1.119 multi-host note (M122): Issue fetching works against GitHub, GitLab, Bitbucket, and GitHub Enterprise. The argument is either a numeric ID (use the configured default remote's host) or a full URL (parsed via parsePrUrl/parseIssueUrl from src/hooks/src/lib/pr-host-parser.ts). Branch on the detected host family for the right CLI: gh issue view (GitHub/GHE), glab issue view (GitLab), bb issue view (Bitbucket). Reference: src/skills/chain-patterns/references/pr-from-platform.md.