Verifies workspace state and staged changes as a read-only preflight. Use before commits or PRs to confirm staged set is clean and correct.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
sanctum:commit-messages)sanctum:pr-prep)Run git status after review to verify workspace state matches expectations.
Run pytest plugins/sanctum/tests/test_git_workspace_review.py to validate review workflow.
Use this skill before workflows that depend on repository state, such as commit message generation, PR preparation, or release notes. Run it once per session or whenever staged changes are modified.
git-review:repo-confirmedgit-review:status-overviewgit-review:code-quality-checkgit-review:diff-statgit-review:diff-detailsMark each item as complete as you finish the corresponding step.
repo-confirmed)Run pwd to confirm you are in the correct repository directory. Execute git status -sb to view the current branch and short status, then capture the branch name and upstream information.
status-overview)Analyze the git status -sb output for staged and unstaged changes. Stage or unstage files so that subsequent workflows operate on the intended diff.
code-quality-check)Run make lint from the repository root to validate code quality
before committing. It checks ruff format, runs the per-plugin ruff
check, and runs bandit. It rewrites nothing: a check that edits the
tree cannot report the diff it was asked to find. When it fails it
names make fix, which is the mutating pair (ruff format plus
ruff check --fix). The root Makefile defines no format target, and
the plugin Makefiles that define one only apply inside their own
directory.
Fix any errors immediately. Do not bypass pre-commit hooks with
--no-verify. This check identifies issues early and avoids
late-stage pipeline failures.
diff-stat)Run git diff --cached --stat for staged changes (or
git diff --stat for unstaged work). Note the number of
files modified and identify hotspots with large insertion
or deletion counts.
When sem is available (see leyline:sem-integration),
also run sem diff --format plain --staged to display an entity-level
summary alongside the stat output. This shows which
functions, classes, and methods changed rather than just
line counts.
diff-details)Run git diff --cached to examine the actual changes. For unstaged work, use git diff. Identify key themes, such as Makefile adjustments or new skill additions, to provide context for downstream summaries.
Complete all progress tracking items. You should have a clear understanding of modified files and areas, and the correct work should be staged. Subsequent workflows can then rely on this context without re-executing git commands.
If pre-commit hooks block a commit, resolve the reported issues instead
of using --no-verify. make lint fixes styling automatically and
surfaces the logical failures that remain. If merge conflicts occur, use
git merge --abort to return to a clean state before retrying.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Shapes turns action-first: action leads, steps numbered, state restated. Use for ADHD-friendly output. Do not use to trim tokens; use response-compression.
The English summary is being prepared. Showing the original description.
Inverts burden of proof for code additions. Use when reviewing PRs, planning refactors, or running unbloat to challenge every addition's necessity.
The English summary is being prepared. Showing the original description.
Tracks per-agent token usage and flags waste in parallel dispatch. Use when evaluating parallel agent efficiency or after a multi-agent run.
The English summary is being prepared. Showing the original description.
Coordinates Claude agent teams via filesystem protocol. Use when orchestrating parallel agents with task dependencies. Do not use for single-agent tasks.
The English summary is being prepared. Showing the original description.
Evaluates API surface design, consistency, and exemplar alignment. Use when reviewing public API changes or before releasing a new API surface.
The English summary is being prepared. Showing the original description.
Selects architecture paradigm via research before scaffolding. Use when architecture is undecided and the choice needs justification and documentation.
The English summary is being prepared. Showing the original description.