dotfiles

Generate a single-file HTML artifact (status report, slide deck, prototype, throwaway editor, flowchart, etc.) and open it in the browser. Use when the user wants a one-off visual artifact instead of markdown — for sharing, reference, or interactive exploration.

Gather context from the codebase and (optionally) the web, then propose multiple ways to move forward with tradeoffs, relative impact, and effort. Use when user wants to explore options, weigh approaches, or asks "what are my options" / "how should I tackle this" before committing to a plan.

Propose a concrete plan to cut a branch and implement a change as one or more atomic commits, grounded in the current codebase and (optionally) outside research. Use when user wants a step-by-step implementation plan, asks "propose a plan" / "how would you implement this", or is ready to move from discussion to execution.

Summarize what shipped over a date range, commit range, or release tag — synthesizes git log, GitHub PRs, and Linear issues into a single markdown brief.

View a Sentry issue by short ID (e.g. PROJECT-123) or URL. Shows details, status, latest event, and tag distribution. Use when user wants to view, check, or look up a Sentry issue, error, or event.

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

Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.

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, or mentions "grill me".

Look up idiomatic approaches, best practices, and common patterns for a given scenario using Exa web search and GitHub code search. Use when user wants to know what's idiomatic, recommended, or common for a bug, architecture decision, library usage, or design pattern.

Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".

View a Linear issue by ID, identifier (e.g. ENG-123), or URL. Shows details, status, comments, and relations. Use when user wants to view, check, or look up a Linear issue or ticket.

Gather and summarize information about a GitHub or Gitea repository — README, docs, examples, structure, and key stats. Use when user wants to learn about a repo, understand a project, or explore a library before using it.

Review a pull request for code quality, security, performance, and adherence to project patterns

View a GitHub/Gitea issue by number, URL, or search query

Stage, commit, push, and open a draft PR

Post-process text to remove LLM-generated writing patterns and make it sound more natural/human-written

Publish the previous output or analysis as a secret GitHub gist

Stage, commit, and push changes

Rebase current branch onto a target branch (default master), resolve merge conflicts, and summarize resolutions

View a GitHub gist by ID or URL

View the PR associated with the current branch or a specified PR number/branch

View a CI run by ID, URL, PR number, or branch (defaults to current branch)