Menu
Turn a vague report into a clear, reproducible, prioritized issue
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Catch bad React in your changes — run react-doctor's deterministic scan and fix what it flags
Run a verifiable security scan (vulns, secrets, misconfig) over code you wrote or deps you added, before calling the work done
Drive a real browser verifiably — navigate, snapshot, act BY INDEX, extract; every step provable
Run multi-agent work as ONE provable causal DAG — parallel subagents, an Orchestrate graph, an immutable spec-seed
Author or connect a Model Context Protocol server so an agent gains new tools
Build automated pipelines that gate merges and ship reliably
| name | issue-triage |
| description | Turn a vague report into a clear, reproducible, prioritized issue |
| version | 1 |
| trust | built-in |
A good issue is half the fix. Whether filing or triaging, drive toward a crisp, reproducible statement of the problem.
Red flag: "it's broken" with no repro, version, or expected behaviour — that's not yet an issue, it's a prompt to gather more.
