Traces code history via git blame and log to explain why code exists in its current form. Use when asked about code history, reasoning behind changes, or "when/why did this change".
Commit changes with smart messages. Supports full and partial commits. Use whenever committing changes or handling pre-commit hook failures.
Use the gh CLI for GitHub interactions, plus setup and pushing. Use when interacting with GitHub, setting up GitHub tools, or pushing to remote.
Universal polyglot linting and per-project config management. Use when you need to lint files, understand tool selection logic, invoke linting from commands/agents, or manage mr-sparkle config.
Resolves git merge conflicts by analyzing intent from both sides. Use when merge conflicts are detected or when git operations fail with conflict errors.
Create a pull request with Problem/Solution format. Can optionally commit first. Use when opening PRs or when branch changes are ready for review.
User's README style preferences — ultra-terse, action-focused, <50 lines. Use when writing or reviewing any README file.
Idioms and gotchas for managing dotfiles with chezmoi — source-state naming/attributes, when to use templates vs modify_ scripts vs run_ scripts, package installation, externals, secrets, and machine differences. Use when adding, editing, or structuring…