Run
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.
Mark each item as complete as you finish the corresponding step.
Run
to confirm you are in the correct repository directory. Execute
to view the current branch and short status, then capture the branch name and upstream information.
Analyze the
output for staged and unstaged changes. Stage or unstage files so that subsequent workflows operate on the intended diff.
Run
to validate code quality before committing. Fix any errors immediately. Do not bypass pre-commit hooks with
. This check identifies issues early and avoids late-stage pipeline failures.
Run
for staged changes (or
for unstaged work). Note the number of files modified and identify hotspots with large insertion or deletion counts.
Run
to examine the actual changes. For unstaged work, use
. 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
. Run
to fix styling errors automatically and use
to isolate logical failures. If merge conflicts occur, use
to return to a clean state before retrying.