Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From sanctum
Verifies git workspace state: repo confirmation, status overview, code quality checks, diff stats/details before commits or PRs.
npx claudepluginhub athola/claude-night-market --plugin sanctumHow this skill is triggered — by the user, by Claude, or both
Slash command
/sanctum:git-workspace-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. [Usage](#usage)
Guides systematic git commits: checks staging status, reviews diffs, splits changes into atomic commits, formats conventional messages. Use before PRs or when committing code.
Runs quality gates, reviews staged changes for issues, and creates a conventional commit. Useful when ready to commit after making changes.
Analyzes git changes, groups files into conventional commit types (feat, fix, refactor, etc.), creates commits, and pushes. Verifies prerequisite review skills have been run before allowing push.
Share bugs, ideas, or general feedback.
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 format && make lint to validate code quality before committing. 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.
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. Run make format to fix styling errors automatically and use make lint to isolate logical failures. If merge conflicts occur, use git merge --abort to return to a clean state before retrying.