.dotfiles

Address review comments left in a live hunk diff session, then commit the fixes locally. Use when the user says to check/address/handle their hunk comments (e.g. /hunk-comments, "address my hunk comments", "I left comments in hunk").

Compact the current conversation into a handoff document for a fresh agent to pick up. Use when the user asks to hand off, wrap up a session, or invokes /handoff.

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, mentions "grill me", or whenever a decision needs the user's input (always use this instead of AskUserQuestion).

Create atomic git commits from outstanding changes with terse, imperative messages. Pass --push to also push to the remote. Use when the user asks to commit (e.g. /commit, "commit this") or commit and push (e.g. /commit --push, "push this", "commit and push").

Pick up a GitHub issue and prepare to work it — read the issue thoroughly, research the codebase, grill the user on every open question until the plan is nailed down, then begin implementing. Use when the user wants to start work on an issue, invokes /pickup, or hands one over from /up-next.

Open a GitHub pull request for the current branch with a concise, template-conformant, PM-readable description. Links the related GitHub issue so it closes on merge and moves it to in-review. Use when the user asks to open or create a PR (e.g. /pr, "open a PR", "create a pull request"). Pass --draft for a draft PR.

Break a plan, spec, or PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when the user wants to convert a plan into issues, create implementation tickets, or break work down into issues.

Distill quick captures from the personal knowledge vault's inbox (~/obsidian/personal/agents/inbox/) into their correct topical home. Proposes a routing plan, applies it after approval, and deletes each inbox note once its content lives in the vault. Use when the user invokes /distill or asks to process/clean up the vault inbox.

Load the operating manual for the shared personal knowledge vault (~/obsidian/personal). Use before reading from or writing to the vault's knowledge - i.e. whenever recording something durable (homelab, projects, etc.), looking up stored knowledge, or capturing a note to the inbox. Invoke as /kb, or auto-load when starting to work with the vault.

On-call debugging workflow. Creates an Obsidian investigation document, researches root cause using Datadog, codebase exploration, and git history, and iteratively refines findings. Use when user invokes /on-call-debug with a Slack link and issue description.

List the work that's ready to pick up by scanning the project board for issues with Status "ready-for-work" and presenting a summarized, ranked shortlist. Use when the user asks "what's next", "what's up next", or invokes /up-next. Can hand a chosen issue to /pickup.

Rebase the current branch onto the latest master/main and force-push with lease. Use when the user asks to rebase onto main/master (e.g. /rebase, "rebase on main", "update my branch off main").

Use when the user wants to stress-test a plan, architecture, or design before implementation. Interrogate assumptions, ask one focused question at a time, branch through the decision tree, and recommend a concrete answer for each open question. Do not start implementing unless the user explicitly switches from design to execution.