Root-cause fix discipline for a debugging session already underway. Use when about to propose or apply a fix for a bug or test failure, when tempted to patch a symptom (add a null check, wrap in try-catch, bump a timeout, add a retry), and when a previous fix didn't work. /diagnosing-bugs builds the repro; this…
Verify an inference-backed, decision-driving claim before it drives a diagnosis, recommendation, external mutation, or user decision. Verify it again when it is challenged or materially reverses.
Plan and run one mechanical edit across a whole population of records. Use when reformatting, renaming, retagging or stripping a field across dozens or thousands of issues, rows, files or board items, and whenever a mass edit needs a dry run, a rollback or proof that it did not touch anything else.
Generate the user's daily standup update from real activity: GitHub PRs and commits, unpushed local work across worktrees, and Claude/Codex/OpenCode session history. Use when the user says /standup, give me my standup, what did I do yesterday, or wants a status summary.
Triage a project board in one pass. Find the candidate tickets, label each agent-ready or need-human, set priority and issue type, and calibrate estimates against approved anchors before any write.
★not rated 2 9d agoA43 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: