Use when the user asks to commit, create a git commit, checkpoint changes, save work to git, or write a commit message.
Use after making changes to run the project's quality gates and report pass or fail for each relevant check.
Generate a centralized, high-altitude mental-model of a codebase as a few whole-system "lens" documents (overview, capabilities, dataflow, codemap, domain) — read instead of the code to understand what a system does. Use when the user wants architecture docs, a codebase overview/mental model, onboarding docs, or to (re)generate `codemap/`. Triggers: "build codemap", "generate architecture docs", "refresh the codemap", "document this codebase".
Use when a task is multi-step, ambiguous, or high-impact and you need an executable implementation plan before editing code.
Use when the user asks to create or update a pull request for the current branch.
Use when rewriting an existing skill so Opus 4.8 (or any frontier reasoning model) executes it with better judgment, less scaffolding, and tighter calibration. Do NOT trigger for new skills from scratch (use skill-creator) or for prompt artifacts (use prompt).
Use when the user asks to merge another branch into the current branch, pull upstream changes without rebasing, or resolve merge conflicts.
Use when the user asks to rebase the current branch onto another branch or update branch history without merging.