Menu
Manage GitHub issues via gh CLI.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Recursive error-fix loop. Use when a bash command fails with a build/test/typecheck error, when the same class of error appears more than once, or when the harness itself needs a persistent rule so the error does not come back. Detect → root-cause → minimal fix → test → lint/typecheck → persist rule (SKILL.md / AGENTS.md / docs/rules) → audit with evidence. Cross-harness (Claude Code, OpenCode, Codex, Gemini, Agy).
Wraps any external CLI so the AI harness can invoke it without context bloat. Captures --help output, documents every subcommand/flag in a compact digest, saves token metrics (raw vs wrapped), and exposes a standardized interface (invoke, explain, audit). Use before calling an unfamiliar CLI or when the harness needs to interact with a CLI repeatedly.
One-shot setup that configures the CLI wrapper ecosystem across ALL AI harnesses (Claude Code, Gemini, Codex, Agy, OpenCode). Creates symlinks from Claude (single source of truth) to every other CLI, registers wrapper skills/agents in each harness, and injects the "prefer wrapped CLI" policy into each CLI's config file. Run once per machine or after adding a new CLI to the ecosystem.
Cross-harness skill that teaches Claude Code, Codex (OpenAI), and Antigravity (Agy) how to use OpenCode as a subagent. Covers delegation triggers, task formatting, provider routing, result handling, and the complete protocol for efficient subagent orchestration.
Automatically routes tasks to the optimal AI agent, model, or provider based on complexity, cost, and capability. Use when implementing features, fixing bugs, or any multi-step development work. Triggers on "implement", "build", "create", "fix", "add feature", "develop", or when the user asks to do any coding task.
Surface opportunities to deepen a codebase. Finds modules that are shallow (thin pass-throughs, anemic types, missing domain modeling) and proposes how to make them deep (rich domain types, co-located behavior, testable seams). Outputs a visual HTML report and then runs an interactive grilling loop that pressure-tests each opportunity. Use when the codebase feels "flat", domain logic leaks into controllers/UI, types carry no behavior, or AI agents struggle to navigate the module boundaries. Integrates with domain-modeling, codebase-design, and ADR workflows.
| name | gh-issue |
| description | Manage GitHub issues via gh CLI. |
Create, list, view, close, reopen, edit, comment, and manage issues.
gh issue create --title "<title>" --body "<body>" --label "<labels>" --assignee "<user>"gh issue list --limit <n> --state <open|closed> --label "<label>" --assignee "<user>"gh issue view <number> --json <fields> or gh issue view --webgh issue close <number> --reason <completed|not_planned>gh issue reopen <number>gh issue edit <number> --title "<title>" --body "<body>" --add-label "<label>" --remove-label "<label>"gh issue comment <number> --body "<body>"gh issue lock <number> / gh issue unlock <number>gh issue pin <number> / gh issue unpin <number>gh issue transfer <number> <repo>gh issue list --milestone "<name>"gh issue list --search "<query>"gh issue statusTriggered when user says "issue", "create issue", "file a bug", "feature request", "list issues".
Use gh issue view --json with specific fields for machine-readable output.