Build a mental model of an unfamiliar codebase — architecture, subsystems, and where to look when changing something. Use when the user is new to a repo, is picking up a project they didn't write, or asks how a codebase is structured or where something lives.
Explain what a PR or branch actually does before you review it — the mental model, the execution path, and what to question. Use when the user needs to understand a change they didn't write, or an agent just produced a large diff or PR.
Restate the last message in plain human language, with no jargon.
Compact the current conversation into a handoff document for another agent to pick up.
Read the latest handoff document and lay out the next steps — short and on-topic. Use when the user asks what's next, what to do next, or to pick up from a handoff.
Make sure the project has a README that is short, on-topic, and covers the instructions someone actually needs — no fluff. Use when the user asks to check, write, or tighten the project's README.
Work through the review comments on a pull request — fix the valid ones, reply to the rest explaining why not. Use when the user says to address, respond to, resolve, or handle PR / review comments, or pastes a PR link and asks to deal with the feedback.
Compress a wall of text into a tight summary. Use when the user says it's too long, too much, "TL;DR", "give me the short version", or that they don't want to read all that.