Status line

Snapshots your work tree before every editing turn and lets you /rollback to any checkpoint.

Formats every file Claude edits with the right formatter for its language.

Give it a goal and success criteria; it plans, delegates, verifies and retries until the criteria pass or it needs you.

/bench runs your benchmarks before and after a change and compares the numbers.

Compares bundle size after each build and warns when it grows.

Shows what share of input tokens came from the prompt cache.

Reads your calendar (private iCal link) so notifications and questions respect meetings and time off, and suggests slots for long jobs.

/ci-watch follows your GitHub Actions run and tells you the moment it passes or fails.

Shows who owns a file (from CODEOWNERS) as Claude edits it.

/concise toggles short, to-the-point answers.

Detects merge-conflict markers and walks you through resolving each one.

Live session cost estimate in the status line, from real token usage.

Warns when console.log, print, debugger or dbg! statements are left in code.

Starts your dev server in the background and shows its errors in a live pane.

After Django model changes, checks for missing migrations and offers to create them.

Collects every failed command and tool error in one pane.

/eli5, /normal and /expert set how deep Claude's explanations go.

A Pomodoro timer in the status line with focus and break cycles.

Shows the current branch, ahead/behind and dirty file count in the status line.

Teaches Claude your project's vocabulary and injects definitions when you use the terms.

Picks up a GitHub, Jira or Linear issue, sizes it with smart-router, works it in a dedicated session and opens the PR.

Turns kubectl apply into a server-side dry run with a diff you approve first.

Claude explains the why behind each change and leaves small TODOs for you to complete yourself.

Runs the linter on each edited file and hands the errors straight back to Claude.