
Trace a code path end-to-end to find bugs. Use when the user reports a bug, unexpected behavior, or wants to understand why something fails.
Interact with GitHub using the `gh` CLI — issues, PRs, CI runs, and API queries.
Relentlessly interview the user about a plan or design.
Resolve jj (Jujutsu) conflicts. Use when jj log/status shows conflicted revisions.
Review or draft technical prose that needs to persuade — design docs, RFDs, proposals, job applications.
Analyze a codebase for improvements across multiple dimensions — test coverage gaps, documentation quality, performance, API ergonomics, correctness. Use when the user wants to find what's missing or could be better in their project.
Query Prometheus/Thanos metrics via the HTTP API. Supports mTLS and PromQL.
Remote control tmux sessions for interactive CLIs (python, gdb, etc.) by sending keystrokes and scraping pane output.
Quick internet research via a web-search-enabled model. Returns summaries with source URLs.
Version control with jj (Jujutsu)
Use when working on the pi coding agent harness or writing pi extensions.
Use when writing skills, CLAUDE.md files, agent prompts, or shell snippets that touch environment variables, API credentials, file creation, or git operations. Covers keeping secrets out of context, safe shell patterns, and credential exposure.
Use when verifying that a skill works before relying on it. Pressure-tests skills with subagents — runs the scenario without the skill, compares to with the skill, iterates until the behavior is reliable.
Use when writing instructions that guide an agent: skills, CLAUDE.md/AGENTS.md files, system prompts, agent prompts. Covers token efficiency, discovery, compliance, and the small repertoire of patterns that earn their keep.
Use when creating or updating CLAUDE.md / AGENTS.md files for a project or a subdirectory. Covers the split between top-level (how to work here) and domain-level (why this exists, what it promises), and the freshness date convention.
Use when creating, editing, or reviewing a skill before it ships. Covers when to write a skill, file layout, the SKILL.md shape, and how to verify it before relying on it.
Create/validate Mermaid diagrams.
Use when you want to work in an isolated jj working copy — parallel task, experimental scratch, subagent with its own tree. Covers creating a workspace, working inside it from anywhere, and cleaning up without losing history.
Quick internet research via a web-search-enabled model. Returns summaries with source URLs.
Deliberate dev → review → fix loop run in-session: implement directly, spawn the `review` skill fresh each round, fix findings or pause for human decisions; 3-round cap.
Check for open obligations on a PR: unresolved comments, self-announced follow-ups, Jira status.
Convert a URL or local file (PDF/DOCX/HTML/etc.) to Markdown, optionally with a summary.
Manage TODOs with the tdo CLI.
Build a mental model of code changes — guided reading order, conceptual grouping, and context.
Review the diff with a subagent, returning a structured report