dotfiles

Review a GitHub pull request against the shared review principles. Accepts "123" (current repo), "repo#123" (current repo's owner), "owner/repo#123", or a URL. Reports Issues and Notes locally, then optionally posts them to the PR as a review.

Review all outstanding changes — or, when the working tree is clean on a non-main branch, the branch's diff from the main branch. Reports Issues (anything that could cause user problems, security risk, or data inconsistency) and optional Notes for further improvement.

Commit all outstanding changes as standalone, logically coherent atomic commits using Conventional Commits.

Review outstanding changes and surface the single most worthwhile improvement to make before committing. Returns one finding — not a list — and only if it's in scope for the change at hand.

Create a GitHub release. Commits and pushes outstanding changes first, then drafts release notes for confirmation. Deployment is only triggered if the project has a release-triggered workflow.

Bootstrap or sync the tobilize approach in the current project — a thin CLAUDE.md that imports @docs/approach.md plus a docs/ tree (architecture/, design/, domain/, plan/) with INDEX.md in each. Discovers project tooling and layout to seed real build commands and an initial architecture overview, not generic placeholders. Also offers method-specific guidance files (DDD, TDD, Hexagonal, SOLID).

Flesh out a draft file into publication-ready prose, respecting any local editorial guidance.

Pick the next task from the project's work-item source, plan its implementation, and execute the plan once approved.

Use the spark CLI to access the user's Spark email data - list emails, search by topic, read threads, check calendar events, find availability, look up contacts, and view team info. Use when the user asks about their emails, calendar, contacts, meetings, or scheduling.