skills

Open, publish, or raise a GitHub pull request. Use when the user asks to create or publish a PR for a GitHub-backed codebase, especially when branches are Linear-issue-prefixed.

Return your work to the parent agent that spawned you. Use when you are a child session that has finished (or reached a checkpoint on) a side-quest and the operator wants the findings returned to the originating session.

Dispatch work to another agent through the mailbox to a named existing peer, or to a new agent wired to reply to you. Use when the operator says "dispatch to <name>" or "dispatch this to a new agent", optionally refining what to send.

Inter-agent mailbox for sending a handoff to another agent session and picking up replies. Use when you need to set up your mailbox, send or reply to another agent, check for or wait on incoming mail, take over an existing mailbox identity (e.g. "take over Alice's mailbox"), or prune stale mailboxes. The fabric beneath the spawn, handback, and dispatch skills.

Spawn a fresh agent session from the current one — hand the conversation off into a new tmux window that continues the work one-way, with no channel back. Use `dispatch` instead when the child must report back.

Generate chart images for markdown documents using the QuickChart API. Use when writing reports, READMEs, changelogs, dashboards, or any markdown output that needs an embedded chart, graph, sparkline, gauge, or data visualisation.

Compact the current conversation into a handoff document for another agent to pick up.

Commit staged changes as a Gitmoji-prefixed Conventional Commit. Use when the user asks to create, draft, or refine a commit message, or to prepare squash-merge commit text.

Generate a markdown changelog for the changes between a fixed point and HEAD, enriched with issue-tracker context. Use when asked for a changelog, release notes, or a summary of merged work over a commit range or date window.

Review the changes since a fixed point along three independent axes — Standards (does the code follow this repo's documented conventions and avoid known smells?), Spec (does it do what the issue/PRD asked?), and Architecture (does the change belong in the system and raise its evolvability — working with the grain of the existing seams, domain model, and layers to leave the architecture cheaper to change next — rather than lowering it?). Runs three parallel sub-agents that never share context and reports them side by side. The strongest architectural opportunity gets a concrete follow-up the operator can run. Use when the user wants to review a branch, a PR, or work-in-progress changes, or asks to "review since X".

Ruthless token-minimization mode plus a "token police" prompt check. Tokens are water; you are dying of thirst. Drops filler, prefers single words and emojis, answers yes/no with ✅/❌, and flags bloated user prompts. Use when user says "desert mode", "token police", "save tokens", "be ruthless", "stop wasting tokens", or invokes /desert-mode.