{"id":"b74de9f3-3341-492a-bc50-3f156ef1efd9","entityType":"agent","slug":"clawhub-athola-nm-sanctum-git-workspace-review","name":"git-workspace-review","canonicalUrl":"https://www.xpersona.co/agent/clawhub-athola-nm-sanctum-git-workspace-review","canonicalPath":"/agent/clawhub-athola-nm-sanctum-git-workspace-review","generatedAt":"2026-10-10T11:54:03.151Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T08:59:54.068Z","emptyReason":null},"description":"Verifies workspace state and staged changes as a read-only preflight. Use before commits or PRs to confirm staged set is clean and correct","descriptionLabel":"Source description","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.5K downloads reported by the source. Last updated 10/10/2026.","installCommand":"clawhub skill install s17emme0e2m3cpf7k2jvp3a84984b8z9:nm-sanctum-git-workspace-review","sourceUrl":"https://clawhub.ai/athola/nm-sanctum-git-workspace-review","homepage":"https://clawhub.ai/athola/skills/nm-sanctum-git-workspace-review","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/athola/nm-sanctum-git-workspace-review","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/athola/skills/nm-sanctum-git-workspace-review","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":64,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"git-workspace-review technical dossier on Xpersona with agent coverage, OPENCLEW support, and live trust metadata."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-10T08:59:54.068Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T08:59:54.068Z","emptyReason":null},"stars":null,"forks":null,"downloads":1541,"packageName":null,"latestVersion":"1.9.19","tractionLabel":"1.5K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T08:59:54.068Z","emptyReason":null},"lastUpdatedAt":"2026-10-10T08:59:54.068Z","lastCrawledAt":"2026-10-10T08:59:54.068Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-11T08:59:54.068Z","lastVerifiedAt":null,"highlights":[{"version":"1.9.19","createdAt":"2026-08-26T13:20:25.943Z","changelog":"Release v1.9.19","fileCount":4,"zipByteSize":4594},{"version":"1.9.17","createdAt":"2026-07-30T05:40:29.966Z","changelog":"Release v1.9.17","fileCount":4,"zipByteSize":4681},{"version":"1.9.16","createdAt":"2026-07-14T19:57:24.609Z","changelog":"Release v1.9.16","fileCount":4,"zipByteSize":4599},{"version":"1.9.14","createdAt":"2026-06-30T18:05:16.397Z","changelog":"Release v1.9.14","fileCount":4,"zipByteSize":4507},{"version":"1.9.13","createdAt":"2026-06-27T16:23:09.661Z","changelog":"Release v1.9.13","fileCount":4,"zipByteSize":4689},{"version":"1.9.12","createdAt":"2026-06-19T03:18:34.203Z","changelog":"Release v1.9.12","fileCount":4,"zipByteSize":4601},{"version":"1.0.3","createdAt":"2026-06-18T15:20:19.797Z","changelog":"Release v1.9.12","fileCount":4,"zipByteSize":4537},{"version":"1.0.2","createdAt":"2026-05-09T02:19:52.286Z","changelog":"Release v1.9.5","fileCount":4,"zipByteSize":4451}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17emme0e2m3cpf7k2jvp3a84984b8z9:nm-sanctum-git-workspace-review","setupComplexity":"low","setupSteps":["Install using `clawhub skill install s17emme0e2m3cpf7k2jvp3a84984b8z9:nm-sanctum-git-workspace-review` in an isolated environment before connecting it to live workloads.","No published capability contract is available yet, so validate auth and request/response behavior manually.","Review the upstream CLAWHUB listing at https://clawhub.ai/athola/nm-sanctum-git-workspace-review before using production credentials."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-git-workspace-review/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-git-workspace-review/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-git-workspace-review/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-git-workspace-review/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-git-workspace-review/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-git-workspace-review/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-10T11:54:03.149Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-git-workspace-review/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-git-workspace-review/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-git-workspace-review/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-git-workspace-review/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T08:59:54.068Z","emptyReason":null},"readme":"Skill: git-workspace-review\n\nOwner: athola\n\nSummary: Verifies workspace state and staged changes as a read-only preflight. Use before commits or PRs to confirm staged set is clean and correct\n\nTags: latest:1.9.19\n\nVersion history:\n\nv1.9.19 | 2026-08-26T13:20:25.943Z | user\n\nRelease v1.9.19\n\nv1.9.17 | 2026-07-30T05:40:29.966Z | user\n\nRelease v1.9.17\n\nv1.9.16 | 2026-07-14T19:57:24.609Z | user\n\nRelease v1.9.16\n\nv1.9.14 | 2026-06-30T18:05:16.397Z | user\n\nRelease v1.9.14\n\nv1.9.13 | 2026-06-27T16:23:09.661Z | user\n\nRelease v1.9.13\n\nv1.9.12 | 2026-06-19T03:18:34.203Z | user\n\nRelease v1.9.12\n\nv1.0.3 | 2026-06-18T15:20:19.797Z | user\n\nRelease v1.9.12\n\nv1.0.2 | 2026-05-09T02:19:52.286Z | user\n\nRelease v1.9.5\n\nv1.0.1 | 2026-05-06T14:21:15.344Z | user\n\nRelease v1.9.4\n\nv1.0.0 | 2026-04-15T19:01:48.112Z | auto\n\n- Initial release of the git-workspace-review skill.\n- Provides structured preflight checks for git workflows, including status verification, code quality, diff statistics, and staged changes review.\n- Includes clear step-by-step progress tracking for robust commit or pull request preparation.\n- Features troubleshooting guidance for pre-commit hooks and merge conflicts.\n- Supports usage in Night Market workflows, with optional enhanced output when sem is available.\n\nArchive index:\n\nArchive v1.9.19: 4 files, 4594 bytes\n\nFiles: modules/git-commands.md (2868b), skill-card.md (1996b), SKILL.md (3722b), _meta.json (151b)\n\nFile v1.9.19:SKILL.md\n\n---\nname: git-workspace-review\ndescription: |\n Verifies workspace state and staged changes as a read-only preflight. Use before commits or PRs to confirm staged set is clean and correct\nversion: 1.9.8\ntriggers:\n - git\n - preflight\n - status\n - diff\n - staged\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# Git Workspace Review\n\n## Table of Contents\n\n1. [Usage](#usage)\n2. [Required Progress Tracking](#required-progress-tracking)\n\n## Verification\n\nRun `git status` after review to verify workspace state matches expectations.\n\n## Testing\n\nRun `pytest plugins/sanctum/tests/test_git_workspace_review.py` to validate review workflow.\n\n## Usage\n\nUse 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.\n\n## Required Progress Tracking\n\n1. `git-review:repo-confirmed`\n2. `git-review:status-overview`\n3. `git-review:code-quality-check`\n4. `git-review:diff-stat`\n5. `git-review:diff-details`\n\nMark each item as complete as you finish the corresponding step.\n\n## Step 1: Confirm Repository (`repo-confirmed`)\n\nRun `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.\n\n## Step 2: Review Status Overview (`status-overview`)\n\nAnalyze the `git status -sb` output for staged and unstaged changes. Stage or unstage files so that subsequent workflows operate on the intended diff.\n\n## Step 3: Check Code Quality (`code-quality-check`)\n\nRun `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.\n\n## Step 4: Review Diff Statistics (`diff-stat`)\n\nRun `git diff --cached --stat` for staged changes (or\n`git diff --stat` for unstaged work). Note the number of\nfiles modified and identify hotspots with large insertion\nor deletion counts.\n\nWhen sem is available (see `leyline:sem-integration`),\nalso run `sem diff --format plain --staged` to display an entity-level\nsummary alongside the stat output. This shows which\nfunctions, classes, and methods changed rather than just\nline counts.\n\n## Step 5: Review Detailed Diff (`diff-details`)\n\nRun `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.\n\n## Exit Criteria\n\nComplete 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.\n\n## Supporting Modules\n\n- [Git commands reference](modules/git-commands.md) - diff, status, branch operations for sanctum workflows\n\n## Troubleshooting\n\nIf 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.\n\nFile v1.9.19:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-sanctum-git-workspace-review\",\n \"version\": \"1.9.19\",\n \"publishedAt\": 1787750425943\n}\n\nFile v1.9.19:modules/git-commands.md\n\n---\nparent_skill: sanctum:shared\nname: git-commands\ndescription: Common git commands used across sanctum workflows\ncategory: patterns\ntags: [git, commands, diff, status]\nestimated_tokens: 200\n---\n\n# Git Commands for Sanctum Workflows\n\n## Repository Confirmation\n\n### Verify Working Directory\n```bash\npwd\n```\nvalidates you are in the correct repository before running git operations.\n\n### Check Branch and Status\n```bash\ngit status -sb\n```\nShows current branch, upstream tracking, and short status in one line.\n\n## Diff Commands\n\n### Staged Changes Statistics\n```bash\ngit diff --cached --stat\n```\nShows file-by-file statistics for staged changes (insertions/deletions).\n\n### Staged Changes Details\n```bash\ngit diff --cached\n```\nFull diff of staged changes for review before commit.\n\n### Unstaged Changes Statistics\n```bash\ngit diff --stat\n```\nFile-by-file statistics for unstaged working directory changes.\n\n### Unstaged Changes Details\n```bash\ngit diff\n```\nFull diff of unstaged working directory changes.\n\n### Branch Comparison Statistics\n```bash\ngit diff --stat origin/main...HEAD\n```\nShows statistics for all commits in current branch since diverging from main.\n\n### Branch Comparison Details\n```bash\ngit diff origin/main...HEAD\n```\nFull diff of all changes in current branch compared to main.\n\n## Status Parsing Patterns\n\n### Extract Branch Name\nFrom `git status -sb` output, the first line shows:\n```\n## branch-name...origin/branch-name [ahead N, behind M]\n```\n\nParse the branch name from the `##` line.\n\n### Identify Staged vs Unstaged\n- Lines starting with `M ` (M-space): staged modification\n- Lines starting with ` M` (space-M): unstaged modification\n- Lines starting with `A ` (A-space): staged new file\n- Lines starting with `??`: untracked file\n\n### Count Changes\nUse `--stat` output to count affected files:\n```\n file1.md | 10 +++++++---\n file2.py | 5 +++++\n 2 files changed, 12 insertions(+), 3 deletions(-)\n```\n\n## Branch Operations\n\n### Get Merge Base\n```bash\ngit merge-base origin/main HEAD\n```\nFinds the common ancestor commit for comparison.\n\n### List Recent Commits\n```bash\ngit log --oneline -10\n```\nShows last 10 commits in compact format.\n\n### Show Commit Details\n```bash\ngit show \n```\nDisplays commit message and diff for a specific commit.\n\n## Best Practices\n\n### Always Run in Sequence\n1. `pwd` - Confirm location\n2. `git status -sb` - Check branch/status\n3. `git diff --cached --stat` - Review staged stats\n4. `git diff --cached` - Review staged details\n\n### Use Limits\n- Always limit `git log` output (e.g., `-10`, `-20`)\n- Use `--stat` before full diffs to understand scope\n- For large diffs, consider `git diff --cached -- `\n\n### Error Handling\n- Check if `git status` shows \"Not a git repository\"\n- Verify upstream tracking exists before comparing to origin\n- Handle empty diffs (no staged changes) gracefully\n\nFile v1.9.19:skill-card.md\n\n## Description:\n\nVerifies workspace state and staged changes as a read-only preflight before commits or PRs.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[athola](https://clawhub.ai/user/athola)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and engineers use this skill to inspect repository status, staged changes, and diffs before commit, PR, or release-note workflows. It helps confirm that the intended files are staged and that code-quality checks have been considered.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill is described as read-only, but evidence.security reports that following it may run Makefile targets, stage or unstage files, and format code.\n\nMitigation: Use only in trusted repositories and require explicit confirmation before commands that change files, change the Git index, or execute project-defined targets.\n\nRisk: Repository-defined quality checks such as make format and make lint can execute local project code or change formatting.\n\nMitigation: Review the relevant Makefile targets before execution and prefer a clean working tree or disposable branch when testing unfamiliar repositories.\n\n## Reference(s):\n\n- [Project homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, guidance]\n\n**Output Format:** [Markdown guidance with inline shell commands]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May prompt the agent to run repository-defined commands and modify the Git index or files when following the workflow.]\n\n## Skill Version(s):\n\n1.9.19 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.9.17: 4 files, 4681 bytes\n\nFiles: modules/git-commands.md (2868b), skill-card.md (2231b), SKILL.md (3722b), _meta.json (151b)\n\nFile v1.9.17:SKILL.md\n\n---\nname: git-workspace-review\ndescription: |\n Verifies workspace state and staged changes as a read-only preflight. Use before commits or PRs to confirm staged set is clean and correct\nversion: 1.9.8\ntriggers:\n - git\n - preflight\n - status\n - diff\n - staged\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# Git Workspace Review\n\n## Table of Contents\n\n1. [Usage](#usage)\n2. [Required Progress Tracking](#required-progress-tracking)\n\n## Verification\n\nRun `git status` after review to verify workspace state matches expectations.\n\n## Testing\n\nRun `pytest plugins/sanctum/tests/test_git_workspace_review.py` to validate review workflow.\n\n## Usage\n\nUse 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.\n\n## Required Progress Tracking\n\n1. `git-review:repo-confirmed`\n2. `git-review:status-overview`\n3. `git-review:code-quality-check`\n4. `git-review:diff-stat`\n5. `git-review:diff-details`\n\nMark each item as complete as you finish the corresponding step.\n\n## Step 1: Confirm Repository (`repo-confirmed`)\n\nRun `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.\n\n## Step 2: Review Status Overview (`status-overview`)\n\nAnalyze the `git status -sb` output for staged and unstaged changes. Stage or unstage files so that subsequent workflows operate on the intended diff.\n\n## Step 3: Check Code Quality (`code-quality-check`)\n\nRun `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.\n\n## Step 4: Review Diff Statistics (`diff-stat`)\n\nRun `git diff --cached --stat` for staged changes (or\n`git diff --stat` for unstaged work). Note the number of\nfiles modified and identify hotspots with large insertion\nor deletion counts.\n\nWhen sem is available (see `leyline:sem-integration`),\nalso run `sem diff --format plain --staged` to display an entity-level\nsummary alongside the stat output. This shows which\nfunctions, classes, and methods changed rather than just\nline counts.\n\n## Step 5: Review Detailed Diff (`diff-details`)\n\nRun `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.\n\n## Exit Criteria\n\nComplete 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.\n\n## Supporting Modules\n\n- [Git commands reference](modules/git-commands.md) - diff, status, branch operations for sanctum workflows\n\n## Troubleshooting\n\nIf 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.\n\nFile v1.9.17:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-sanctum-git-workspace-review\",\n \"version\": \"1.9.17\",\n \"publishedAt\": 1785390029966\n}\n\nFile v1.9.17:modules/git-commands.md\n\n---\nparent_skill: sanctum:shared\nname: git-commands\ndescription: Common git commands used across sanctum workflows\ncategory: patterns\ntags: [git, commands, diff, status]\nestimated_tokens: 200\n---\n\n# Git Commands for Sanctum Workflows\n\n## Repository Confirmation\n\n### Verify Working Directory\n```bash\npwd\n```\nvalidates you are in the correct repository before running git operations.\n\n### Check Branch and Status\n```bash\ngit status -sb\n```\nShows current branch, upstream tracking, and short status in one line.\n\n## Diff Commands\n\n### Staged Changes Statistics\n```bash\ngit diff --cached --stat\n```\nShows file-by-file statistics for staged changes (insertions/deletions).\n\n### Staged Changes Details\n```bash\ngit diff --cached\n```\nFull diff of staged changes for review before commit.\n\n### Unstaged Changes Statistics\n```bash\ngit diff --stat\n```\nFile-by-file statistics for unstaged working directory changes.\n\n### Unstaged Changes Details\n```bash\ngit diff\n```\nFull diff of unstaged working directory changes.\n\n### Branch Comparison Statistics\n```bash\ngit diff --stat origin/main...HEAD\n```\nShows statistics for all commits in current branch since diverging from main.\n\n### Branch Comparison Details\n```bash\ngit diff origin/main...HEAD\n```\nFull diff of all changes in current branch compared to main.\n\n## Status Parsing Patterns\n\n### Extract Branch Name\nFrom `git status -sb` output, the first line shows:\n```\n## branch-name...origin/branch-name [ahead N, behind M]\n```\n\nParse the branch name from the `##` line.\n\n### Identify Staged vs Unstaged\n- Lines starting with `M ` (M-space): staged modification\n- Lines starting with ` M` (space-M): unstaged modification\n- Lines starting with `A ` (A-space): staged new file\n- Lines starting with `??`: untracked file\n\n### Count Changes\nUse `--stat` output to count affected files:\n```\n file1.md | 10 +++++++---\n file2.py | 5 +++++\n 2 files changed, 12 insertions(+), 3 deletions(-)\n```\n\n## Branch Operations\n\n### Get Merge Base\n```bash\ngit merge-base origin/main HEAD\n```\nFinds the common ancestor commit for comparison.\n\n### List Recent Commits\n```bash\ngit log --oneline -10\n```\nShows last 10 commits in compact format.\n\n### Show Commit Details\n```bash\ngit show \n```\nDisplays commit message and diff for a specific commit.\n\n## Best Practices\n\n### Always Run in Sequence\n1. `pwd` - Confirm location\n2. `git status -sb` - Check branch/status\n3. `git diff --cached --stat` - Review staged stats\n4. `git diff --cached` - Review staged details\n\n### Use Limits\n- Always limit `git log` output (e.g., `-10`, `-20`)\n- Use `--stat` before full diffs to understand scope\n- For large diffs, consider `git diff --cached -- `\n\n### Error Handling\n- Check if `git status` shows \"Not a git repository\"\n- Verify upstream tracking exists before comparing to origin\n- Handle empty diffs (no staged changes) gracefully\n\nFile v1.9.17:skill-card.md\n\n## Description:
\nVerifies workspace state and staged changes as a preflight before commits or PRs to confirm the staged set is clean and correct.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[athola](https://clawhub.ai/user/athola)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and engineers use this skill before commits, pull requests, or release-note preparation to inspect repository status, staged and unstaged diffs, and the intended change set.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill is described as read-only but includes steps that can change staging state or rewrite repository files through formatting and lint-fix workflows.
\nMitigation: Use it only when repository changes are intended, and require explicit user approval before staging, unstaging, formatting, linting, or fixing files.
\nRisk: Git diff and status guidance can expose sensitive uncommitted code or local file names in agent output.
\nMitigation: Review the repository context before sharing output outside the workspace and avoid pasting confidential diffs into external channels.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-sanctum-git-workspace-review)
\n- [metadata.clawdis homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum)
\n- [modules/git-commands.md](modules/git-commands.md)
\n\n\n## Skill Output:
\n**Output Type(s):** [Analysis, Shell commands, Guidance]
\n**Output Format:** [Markdown with inline shell commands]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May include repository status summaries, staged or unstaged diff observations, and recommended next actions.]
\n\n## Skill Version(s):
\n1.9.17 (source: server release evidence; artifact frontmatter says 1.9.8)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.9.16: 4 files, 4599 bytes\n\nFiles: modules/git-commands.md (2868b), skill-card.md (2041b), SKILL.md (3722b), _meta.json (151b)\n\nFile v1.9.16:SKILL.md\n\n---\nname: git-workspace-review\ndescription: |\n Verifies workspace state and staged changes as a read-only preflight. Use before commits or PRs to confirm staged set is clean and correct\nversion: 1.9.8\ntriggers:\n - git\n - preflight\n - status\n - diff\n - staged\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# Git Workspace Review\n\n## Table of Contents\n\n1. [Usage](#usage)\n2. [Required Progress Tracking](#required-progress-tracking)\n\n## Verification\n\nRun `git status` after review to verify workspace state matches expectations.\n\n## Testing\n\nRun `pytest plugins/sanctum/tests/test_git_workspace_review.py` to validate review workflow.\n\n## Usage\n\nUse 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.\n\n## Required Progress Tracking\n\n1. `git-review:repo-confirmed`\n2. `git-review:status-overview`\n3. `git-review:code-quality-check`\n4. `git-review:diff-stat`\n5. `git-review:diff-details`\n\nMark each item as complete as you finish the corresponding step.\n\n## Step 1: Confirm Repository (`repo-confirmed`)\n\nRun `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.\n\n## Step 2: Review Status Overview (`status-overview`)\n\nAnalyze the `git status -sb` output for staged and unstaged changes. Stage or unstage files so that subsequent workflows operate on the intended diff.\n\n## Step 3: Check Code Quality (`code-quality-check`)\n\nRun `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.\n\n## Step 4: Review Diff Statistics (`diff-stat`)\n\nRun `git diff --cached --stat` for staged changes (or\n`git diff --stat` for unstaged work). Note the number of\nfiles modified and identify hotspots with large insertion\nor deletion counts.\n\nWhen sem is available (see `leyline:sem-integration`),\nalso run `sem diff --format plain --staged` to display an entity-level\nsummary alongside the stat output. This shows which\nfunctions, classes, and methods changed rather than just\nline counts.\n\n## Step 5: Review Detailed Diff (`diff-details`)\n\nRun `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.\n\n## Exit Criteria\n\nComplete 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.\n\n## Supporting Modules\n\n- [Git commands reference](modules/git-commands.md) - diff, status, branch operations for sanctum workflows\n\n## Troubleshooting\n\nIf 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.\n\nFile v1.9.16:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-sanctum-git-workspace-review\",\n \"version\": \"1.9.16\",\n \"publishedAt\": 1784059044609\n}\n\nFile v1.9.16:modules/git-commands.md\n\n---\nparent_skill: sanctum:shared\nname: git-commands\ndescription: Common git commands used across sanctum workflows\ncategory: patterns\ntags: [git, commands, diff, status]\nestimated_tokens: 200\n---\n\n# Git Commands for Sanctum Workflows\n\n## Repository Confirmation\n\n### Verify Working Directory\n```bash\npwd\n```\nvalidates you are in the correct repository before running git operations.\n\n### Check Branch and Status\n```bash\ngit status -sb\n```\nShows current branch, upstream tracking, and short status in one line.\n\n## Diff Commands\n\n### Staged Changes Statistics\n```bash\ngit diff --cached --stat\n```\nShows file-by-file statistics for staged changes (insertions/deletions).\n\n### Staged Changes Details\n```bash\ngit diff --cached\n```\nFull diff of staged changes for review before commit.\n\n### Unstaged Changes Statistics\n```bash\ngit diff --stat\n```\nFile-by-file statistics for unstaged working directory changes.\n\n### Unstaged Changes Details\n```bash\ngit diff\n```\nFull diff of unstaged working directory changes.\n\n### Branch Comparison Statistics\n```bash\ngit diff --stat origin/main...HEAD\n```\nShows statistics for all commits in current branch since diverging from main.\n\n### Branch Comparison Details\n```bash\ngit diff origin/main...HEAD\n```\nFull diff of all changes in current branch compared to main.\n\n## Status Parsing Patterns\n\n### Extract Branch Name\nFrom `git status -sb` output, the first line shows:\n```\n## branch-name...origin/branch-name [ahead N, behind M]\n```\n\nParse the branch name from the `##` line.\n\n### Identify Staged vs Unstaged\n- Lines starting with `M ` (M-space): staged modification\n- Lines starting with ` M` (space-M): unstaged modification\n- Lines starting with `A ` (A-space): staged new file\n- Lines starting with `??`: untracked file\n\n### Count Changes\nUse `--stat` output to count affected files:\n```\n file1.md | 10 +++++++---\n file2.py | 5 +++++\n 2 files changed, 12 insertions(+), 3 deletions(-)\n```\n\n## Branch Operations\n\n### Get Merge Base\n```bash\ngit merge-base origin/main HEAD\n```\nFinds the common ancestor commit for comparison.\n\n### List Recent Commits\n```bash\ngit log --oneline -10\n```\nShows last 10 commits in compact format.\n\n### Show Commit Details\n```bash\ngit show \n```\nDisplays commit message and diff for a specific commit.\n\n## Best Practices\n\n### Always Run in Sequence\n1. `pwd` - Confirm location\n2. `git status -sb` - Check branch/status\n3. `git diff --cached --stat` - Review staged stats\n4. `git diff --cached` - Review staged details\n\n### Use Limits\n- Always limit `git log` output (e.g., `-10`, `-20`)\n- Use `--stat` before full diffs to understand scope\n- For large diffs, consider `git diff --cached -- `\n\n### Error Handling\n- Check if `git status` shows \"Not a git repository\"\n- Verify upstream tracking exists before comparing to origin\n- Handle empty diffs (no staged changes) gracefully\n\nFile v1.9.16:skill-card.md\n\n## Description:
\nVerifies workspace state and staged changes as a preflight before commits or PRs.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[athola](https://clawhub.ai/user/athola)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and engineers use this skill to inspect repository status, staged changes, and diffs before commit, pull request, or release-note workflows.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The security summary says the skill claims to be read-only while instructing agents to stage or unstage files, run Makefile targets, and fix files.
\nMitigation: Require explicit confirmation before staging, unstaging, formatting, linting, merge-abort, make commands, or file edits.
\nRisk: The security verdict is suspicious for normal use because the skill can move from repository inspection into modifying the workspace.
\nMitigation: Install only when that behavior is intended, and narrow triggers or edit the skill if a truly read-only review helper is required.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-sanctum-git-workspace-review)
\n- [ClawHub metadata homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum)
\n\n\n## Skill Output:
\n**Output Type(s):** [guidance, shell commands, markdown]
\n**Output Format:** [Markdown with inline shell commands]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May include git status, diff statistics, detailed diff review notes, and code-quality check results.]
\n\n## Skill Version(s):
\n1.9.16 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.9.14: 4 files, 4507 bytes\n\nFiles: modules/git-commands.md (2868b), skill-card.md (1809b), SKILL.md (3722b), _meta.json (151b)\n\nFile v1.9.14:SKILL.md\n\n---\nname: git-workspace-review\ndescription: |\n Verifies workspace state and staged changes as a read-only preflight. Use before commits or PRs to confirm staged set is clean and correct\nversion: 1.9.8\ntriggers:\n - git\n - preflight\n - status\n - diff\n - staged\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# Git Workspace Review\n\n## Table of Contents\n\n1. [Usage](#usage)\n2. [Required Progress Tracking](#required-progress-tracking)\n\n## Verification\n\nRun `git status` after review to verify workspace state matches expectations.\n\n## Testing\n\nRun `pytest plugins/sanctum/tests/test_git_workspace_review.py` to validate review workflow.\n\n## Usage\n\nUse 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.\n\n## Required Progress Tracking\n\n1. `git-review:repo-confirmed`\n2. `git-review:status-overview`\n3. `git-review:code-quality-check`\n4. `git-review:diff-stat`\n5. `git-review:diff-details`\n\nMark each item as complete as you finish the corresponding step.\n\n## Step 1: Confirm Repository (`repo-confirmed`)\n\nRun `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.\n\n## Step 2: Review Status Overview (`status-overview`)\n\nAnalyze the `git status -sb` output for staged and unstaged changes. Stage or unstage files so that subsequent workflows operate on the intended diff.\n\n## Step 3: Check Code Quality (`code-quality-check`)\n\nRun `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.\n\n## Step 4: Review Diff Statistics (`diff-stat`)\n\nRun `git diff --cached --stat` for staged changes (or\n`git diff --stat` for unstaged work). Note the number of\nfiles modified and identify hotspots with large insertion\nor deletion counts.\n\nWhen sem is available (see `leyline:sem-integration`),\nalso run `sem diff --format plain --staged` to display an entity-level\nsummary alongside the stat output. This shows which\nfunctions, classes, and methods changed rather than just\nline counts.\n\n## Step 5: Review Detailed Diff (`diff-details`)\n\nRun `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.\n\n## Exit Criteria\n\nComplete 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.\n\n## Supporting Modules\n\n- [Git commands reference](modules/git-commands.md) - diff, status, branch operations for sanctum workflows\n\n## Troubleshooting\n\nIf 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.\n\nFile v1.9.14:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-sanctum-git-workspace-review\",\n \"version\": \"1.9.14\",\n \"publishedAt\": 1782842716397\n}\n\nFile v1.9.14:modules/git-commands.md\n\n---\nparent_skill: sanctum:shared\nname: git-commands\ndescription: Common git commands used across sanctum workflows\ncategory: patterns\ntags: [git, commands, diff, status]\nestimated_tokens: 200\n---\n\n# Git Commands for Sanctum Workflows\n\n## Repository Confirmation\n\n### Verify Working Directory\n```bash\npwd\n```\nvalidates you are in the correct repository before running git operations.\n\n### Check Branch and Status\n```bash\ngit status -sb\n```\nShows current branch, upstream tracking, and short status in one line.\n\n## Diff Commands\n\n### Staged Changes Statistics\n```bash\ngit diff --cached --stat\n```\nShows file-by-file statistics for staged changes (insertions/deletions).\n\n### Staged Changes Details\n```bash\ngit diff --cached\n```\nFull diff of staged changes for review before commit.\n\n### Unstaged Changes Statistics\n```bash\ngit diff --stat\n```\nFile-by-file statistics for unstaged working directory changes.\n\n### Unstaged Changes Details\n```bash\ngit diff\n```\nFull diff of unstaged working directory changes.\n\n### Branch Comparison Statistics\n```bash\ngit diff --stat origin/main...HEAD\n```\nShows statistics for all commits in current branch since diverging from main.\n\n### Branch Comparison Details\n```bash\ngit diff origin/main...HEAD\n```\nFull diff of all changes in current branch compared to main.\n\n## Status Parsing Patterns\n\n### Extract Branch Name\nFrom `git status -sb` output, the first line shows:\n```\n## branch-name...origin/branch-name [ahead N, behind M]\n```\n\nParse the branch name from the `##` line.\n\n### Identify Staged vs Unstaged\n- Lines starting with `M ` (M-space): staged modification\n- Lines starting with ` M` (space-M): unstaged modification\n- Lines starting with `A ` (A-space): staged new file\n- Lines starting with `??`: untracked file\n\n### Count Changes\nUse `--stat` output to count affected files:\n```\n file1.md | 10 +++++++---\n file2.py | 5 +++++\n 2 files changed, 12 insertions(+), 3 deletions(-)\n```\n\n## Branch Operations\n\n### Get Merge Base\n```bash\ngit merge-base origin/main HEAD\n```\nFinds the common ancestor commit for comparison.\n\n### List Recent Commits\n```bash\ngit log --oneline -10\n```\nShows last 10 commits in compact format.\n\n### Show Commit Details\n```bash\ngit show \n```\nDisplays commit message and diff for a specific commit.\n\n## Best Practices\n\n### Always Run in Sequence\n1. `pwd` - Confirm location\n2. `git status -sb` - Check branch/status\n3. `git diff --cached --stat` - Review staged stats\n4. `git diff --cached` - Review staged details\n\n### Use Limits\n- Always limit `git log` output (e.g., `-10`, `-20`)\n- Use `--stat` before full diffs to understand scope\n- For large diffs, consider `git diff --cached -- `\n\n### Error Handling\n- Check if `git status` shows \"Not a git repository\"\n- Verify upstream tracking exists before comparing to origin\n- Handle empty diffs (no staged changes) gracefully\n\nFile v1.9.14:skill-card.md\n\n## Description:
\nVerifies workspace state and staged changes as a read-only preflight before commits or PRs.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[athola](https://clawhub.ai/user/athola)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and engineers use this skill before commits, pull requests, or release preparation to inspect repository status, staged and unstaged changes, diff statistics, and detailed diffs.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The security evidence says the skill is framed as read-only while instructing agents to make repository-changing fixes and staging changes.
\nMitigation: Before use, require the agent to ask for confirmation before staging, unstaging, formatting, fixing files, or aborting merges.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-sanctum-git-workspace-review)
\n- [Night Market Sanctum homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, guidance]
\n**Output Format:** [Markdown guidance with git and shell command snippets]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [No API keys or credential environment variables were detected in the provided artifact.]
\n\n## Skill Version(s):
\n1.9.14 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.9.13: 4 files, 4689 bytes\n\nFiles: modules/git-commands.md (2868b), skill-card.md (2274b), SKILL.md (3722b), _meta.json (151b)\n\nFile v1.9.13:SKILL.md\n\n---\nname: git-workspace-review\ndescription: |\n Verifies workspace state and staged changes as a read-only preflight. Use before commits or PRs to confirm staged set is clean and correct\nversion: 1.9.8\ntriggers:\n - git\n - preflight\n - status\n - diff\n - staged\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# Git Workspace Review\n\n## Table of Contents\n\n1. [Usage](#usage)\n2. [Required Progress Tracking](#required-progress-tracking)\n\n## Verification\n\nRun `git status` after review to verify workspace state matches expectations.\n\n## Testing\n\nRun `pytest plugins/sanctum/tests/test_git_workspace_review.py` to validate review workflow.\n\n## Usage\n\nUse 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.\n\n## Required Progress Tracking\n\n1. `git-review:repo-confirmed`\n2. `git-review:status-overview`\n3. `git-review:code-quality-check`\n4. `git-review:diff-stat`\n5. `git-review:diff-details`\n\nMark each item as complete as you finish the corresponding step.\n\n## Step 1: Confirm Repository (`repo-confirmed`)\n\nRun `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.\n\n## Step 2: Review Status Overview (`status-overview`)\n\nAnalyze the `git status -sb` output for staged and unstaged changes. Stage or unstage files so that subsequent workflows operate on the intended diff.\n\n## Step 3: Check Code Quality (`code-quality-check`)\n\nRun `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.\n\n## Step 4: Review Diff Statistics (`diff-stat`)\n\nRun `git diff --cached --stat` for staged changes (or\n`git diff --stat` for unstaged work). Note the number of\nfiles modified and identify hotspots with large insertion\nor deletion counts.\n\nWhen sem is available (see `leyline:sem-integration`),\nalso run `sem diff --format plain --staged` to display an entity-level\nsummary alongside the stat output. This shows which\nfunctions, classes, and methods changed rather than just\nline counts.\n\n## Step 5: Review Detailed Diff (`diff-details`)\n\nRun `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.\n\n## Exit Criteria\n\nComplete 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.\n\n## Supporting Modules\n\n- [Git commands reference](modules/git-commands.md) - diff, status, branch operations for sanctum workflows\n\n## Troubleshooting\n\nIf 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.\n\nFile v1.9.13:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-sanctum-git-workspace-review\",\n \"version\": \"1.9.13\",\n \"publishedAt\": 1782577389661\n}\n\nFile v1.9.13:modules/git-commands.md\n\n---\nparent_skill: sanctum:shared\nname: git-commands\ndescription: Common git commands used across sanctum workflows\ncategory: patterns\ntags: [git, commands, diff, status]\nestimated_tokens: 200\n---\n\n# Git Commands for Sanctum Workflows\n\n## Repository Confirmation\n\n### Verify Working Directory\n```bash\npwd\n```\nvalidates you are in the correct repository before running git operations.\n\n### Check Branch and Status\n```bash\ngit status -sb\n```\nShows current branch, upstream tracking, and short status in one line.\n\n## Diff Commands\n\n### Staged Changes Statistics\n```bash\ngit diff --cached --stat\n```\nShows file-by-file statistics for staged changes (insertions/deletions).\n\n### Staged Changes Details\n```bash\ngit diff --cached\n```\nFull diff of staged changes for review before commit.\n\n### Unstaged Changes Statistics\n```bash\ngit diff --stat\n```\nFile-by-file statistics for unstaged working directory changes.\n\n### Unstaged Changes Details\n```bash\ngit diff\n```\nFull diff of unstaged working directory changes.\n\n### Branch Comparison Statistics\n```bash\ngit diff --stat origin/main...HEAD\n```\nShows statistics for all commits in current branch since diverging from main.\n\n### Branch Comparison Details\n```bash\ngit diff origin/main...HEAD\n```\nFull diff of all changes in current branch compared to main.\n\n## Status Parsing Patterns\n\n### Extract Branch Name\nFrom `git status -sb` output, the first line shows:\n```\n## branch-name...origin/branch-name [ahead N, behind M]\n```\n\nParse the branch name from the `##` line.\n\n### Identify Staged vs Unstaged\n- Lines starting with `M ` (M-space): staged modification\n- Lines starting with ` M` (space-M): unstaged modification\n- Lines starting with `A ` (A-space): staged new file\n- Lines starting with `??`: untracked file\n\n### Count Changes\nUse `--stat` output to count affected files:\n```\n file1.md | 10 +++++++---\n file2.py | 5 +++++\n 2 files changed, 12 insertions(+), 3 deletions(-)\n```\n\n## Branch Operations\n\n### Get Merge Base\n```bash\ngit merge-base origin/main HEAD\n```\nFinds the common ancestor commit for comparison.\n\n### List Recent Commits\n```bash\ngit log --oneline -10\n```\nShows last 10 commits in compact format.\n\n### Show Commit Details\n```bash\ngit show \n```\nDisplays commit message and diff for a specific commit.\n\n## Best Practices\n\n### Always Run in Sequence\n1. `pwd` - Confirm location\n2. `git status -sb` - Check branch/status\n3. `git diff --cached --stat` - Review staged stats\n4. `git diff --cached` - Review staged details\n\n### Use Limits\n- Always limit `git log` output (e.g., `-10`, `-20`)\n- Use `--stat` before full diffs to understand scope\n- For large diffs, consider `git diff --cached -- `\n\n### Error Handling\n- Check if `git status` shows \"Not a git repository\"\n- Verify upstream tracking exists before comparing to origin\n- Handle empty diffs (no staged changes) gracefully\n\nFile v1.9.13:skill-card.md\n\n## Description:
\nVerifies workspace state and staged changes as a read-only preflight for commits, pull requests, and release preparation.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[athola](https://clawhub.ai/user/athola)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and engineers use this skill before commits, pull requests, or release notes to inspect repository state, staged changes, and relevant diffs. It helps confirm that the intended work is staged and that code quality checks have been considered.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill is described as read-only but can lead an agent to stage or unstage files and run formatting fixes.
\nMitigation: Require explicit confirmation before staging, unstaging, formatting, or applying fixes, and review git status and diffs before continuing.
\nRisk: Project-defined formatting and lint commands may modify files or execute repository-specific tooling.
\nMitigation: Run the skill only in trusted repositories or an isolated workspace, and inspect the relevant build scripts before allowing automated commands.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-sanctum-git-workspace-review)
\n- [ClawHub metadata homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum)
\n- [Git commands reference](modules/git-commands.md)
\n\n\n## Skill Output:
\n**Output Type(s):** [Analysis, Shell commands, Guidance]
\n**Output Format:** [Markdown guidance with inline shell commands and a progress checklist]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May involve git status, diff, staging, formatting, and lint commands depending on agent execution policy.]
\n\n## Skill Version(s):
\n1.9.13 (source: server release metadata; artifact frontmatter lists 1.9.8)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.9.12: 4 files, 4601 bytes\n\nFiles: modules/git-commands.md (2868b), skill-card.md (2145b), SKILL.md (3722b), _meta.json (151b)\n\nFile v1.9.12:SKILL.md\n\n---\nname: git-workspace-review\ndescription: |\n Verifies workspace state and staged changes as a read-only preflight. Use before commits or PRs to confirm staged set is clean and correct\nversion: 1.9.8\ntriggers:\n - git\n - preflight\n - status\n - diff\n - staged\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# Git Workspace Review\n\n## Table of Contents\n\n1. [Usage](#usage)\n2. [Required Progress Tracking](#required-progress-tracking)\n\n## Verification\n\nRun `git status` after review to verify workspace state matches expectations.\n\n## Testing\n\nRun `pytest plugins/sanctum/tests/test_git_workspace_review.py` to validate review workflow.\n\n## Usage\n\nUse 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.\n\n## Required Progress Tracking\n\n1. `git-review:repo-confirmed`\n2. `git-review:status-overview`\n3. `git-review:code-quality-check`\n4. `git-review:diff-stat`\n5. `git-review:diff-details`\n\nMark each item as complete as you finish the corresponding step.\n\n## Step 1: Confirm Repository (`repo-confirmed`)\n\nRun `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.\n\n## Step 2: Review Status Overview (`status-overview`)\n\nAnalyze the `git status -sb` output for staged and unstaged changes. Stage or unstage files so that subsequent workflows operate on the intended diff.\n\n## Step 3: Check Code Quality (`code-quality-check`)\n\nRun `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.\n\n## Step 4: Review Diff Statistics (`diff-stat`)\n\nRun `git diff --cached --stat` for staged changes (or\n`git diff --stat` for unstaged work). Note the number of\nfiles modified and identify hotspots with large insertion\nor deletion counts.\n\nWhen sem is available (see `leyline:sem-integration`),\nalso run `sem diff --format plain --staged` to display an entity-level\nsummary alongside the stat output. This shows which\nfunctions, classes, and methods changed rather than just\nline counts.\n\n## Step 5: Review Detailed Diff (`diff-details`)\n\nRun `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.\n\n## Exit Criteria\n\nComplete 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.\n\n## Supporting Modules\n\n- [Git commands reference](modules/git-commands.md) - diff, status, branch operations for sanctum workflows\n\n## Troubleshooting\n\nIf 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.\n\nFile v1.9.12:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-sanctum-git-workspace-review\",\n \"version\": \"1.9.12\",\n \"publishedAt\": 1781839114203\n}\n\nFile v1.9.12:modules/git-commands.md\n\n---\nparent_skill: sanctum:shared\nname: git-commands\ndescription: Common git commands used across sanctum workflows\ncategory: patterns\ntags: [git, commands, diff, status]\nestimated_tokens: 200\n---\n\n# Git Commands for Sanctum Workflows\n\n## Repository Confirmation\n\n### Verify Working Directory\n```bash\npwd\n```\nvalidates you are in the correct repository before running git operations.\n\n### Check Branch and Status\n```bash\ngit status -sb\n```\nShows current branch, upstream tracking, and short status in one line.\n\n## Diff Commands\n\n### Staged Changes Statistics\n```bash\ngit diff --cached --stat\n```\nShows file-by-file statistics for staged changes (insertions/deletions).\n\n### Staged Changes Details\n```bash\ngit diff --cached\n```\nFull diff of staged changes for review before commit.\n\n### Unstaged Changes Statistics\n```bash\ngit diff --stat\n```\nFile-by-file statistics for unstaged working directory changes.\n\n### Unstaged Changes Details\n```bash\ngit diff\n```\nFull diff of unstaged working directory changes.\n\n### Branch Comparison Statistics\n```bash\ngit diff --stat origin/main...HEAD\n```\nShows statistics for all commits in current branch since diverging from main.\n\n### Branch Comparison Details\n```bash\ngit diff origin/main...HEAD\n```\nFull diff of all changes in current branch compared to main.\n\n## Status Parsing Patterns\n\n### Extract Branch Name\nFrom `git status -sb` output, the first line shows:\n```\n## branch-name...origin/branch-name [ahead N, behind M]\n```\n\nParse the branch name from the `##` line.\n\n### Identify Staged vs Unstaged\n- Lines starting with `M ` (M-space): staged modification\n- Lines starting with ` M` (space-M): unstaged modification\n- Lines starting with `A ` (A-space): staged new file\n- Lines starting with `??`: untracked file\n\n### Count Changes\nUse `--stat` output to count affected files:\n```\n file1.md | 10 +++++++---\n file2.py | 5 +++++\n 2 files changed, 12 insertions(+), 3 deletions(-)\n```\n\n## Branch Operations\n\n### Get Merge Base\n```bash\ngit merge-base origin/main HEAD\n```\nFinds the common ancestor commit for comparison.\n\n### List Recent Commits\n```bash\ngit log --oneline -10\n```\nShows last 10 commits in compact format.\n\n### Show Commit Details\n```bash\ngit show \n```\nDisplays commit message and diff for a specific commit.\n\n## Best Practices\n\n### Always Run in Sequence\n1. `pwd` - Confirm location\n2. `git status -sb` - Check branch/status\n3. `git diff --cached --stat` - Review staged stats\n4. `git diff --cached` - Review staged details\n\n### Use Limits\n- Always limit `git log` output (e.g., `-10`, `-20`)\n- Use `--stat` before full diffs to understand scope\n- For large diffs, consider `git diff --cached -- `\n\n### Error Handling\n- Check if `git status` shows \"Not a git repository\"\n- Verify upstream tracking exists before comparing to origin\n- Handle empty diffs (no staged changes) gracefully\n\nFile v1.9.12:skill-card.md\n\n## Description:
\nVerifies workspace state and staged changes as a read-only preflight before commits or PRs.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[athola](https://clawhub.ai/user/athola)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and engineering agents use this skill before commit, pull request, or release-note workflows to inspect repository status, staged changes, diff statistics, and detailed diffs.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill is described as read-only but includes workflow steps that can format files or change staged state.
\nMitigation: Treat mutating actions as proposed commands and require explicit confirmation before formatting, staging, unstaging, or aborting merges.
\nRisk: A review can be misleading if status or diffs are collected from the wrong repository, branch, or staging state.
\nMitigation: Confirm the working directory, branch, upstream, and staged versus unstaged changes before relying on the review.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/athola/nm-sanctum-git-workspace-review)
\n- [ClawHub publisher profile](https://clawhub.ai/user/athola)
\n- [Project homepage from ClawHub metadata](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum)
\n\n\n## Skill Output:
\n**Output Type(s):** [guidance, shell commands, markdown]
\n**Output Format:** [Markdown guidance with inline shell commands and review checkpoints]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [The skill can lead an agent to run formatters and adjust staged files; require approval before mutating commands.]
\n\n## Skill Version(s):
\n1.9.12 (source: ClawHub release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.3: 4 files, 4537 bytes\n\nFiles: modules/git-commands.md (2868b), skill-card.md (1903b), SKILL.md (3722b), _meta.json (150b)\n\nFile v1.0.3:SKILL.md\n\n---\nname: git-workspace-review\ndescription: |\n Verifies workspace state and staged changes as a read-only preflight. Use before commits or PRs to confirm staged set is clean and correct\nversion: 1.9.8\ntriggers:\n - git\n - preflight\n - status\n - diff\n - staged\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# Git Workspace Review\n\n## Table of Contents\n\n1. [Usage](#usage)\n2. [Required Progress Tracking](#required-progress-tracking)\n\n## Verification\n\nRun `git status` after review to verify workspace state matches expectations.\n\n## Testing\n\nRun `pytest plugins/sanctum/tests/test_git_workspace_review.py` to validate review workflow.\n\n## Usage\n\nUse 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.\n\n## Required Progress Tracking\n\n1. `git-review:repo-confirmed`\n2. `git-review:status-overview`\n3. `git-review:code-quality-check`\n4. `git-review:diff-stat`\n5. `git-review:diff-details`\n\nMark each item as complete as you finish the corresponding step.\n\n## Step 1: Confirm Repository (`repo-confirmed`)\n\nRun `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.\n\n## Step 2: Review Status Overview (`status-overview`)\n\nAnalyze the `git status -sb` output for staged and unstaged changes. Stage or unstage files so that subsequent workflows operate on the intended diff.\n\n## Step 3: Check Code Quality (`code-quality-check`)\n\nRun `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.\n\n## Step 4: Review Diff Statistics (`diff-stat`)\n\nRun `git diff --cached --stat` for staged changes (or\n`git diff --stat` for unstaged work). Note the number of\nfiles modified and identify hotspots with large insertion\nor deletion counts.\n\nWhen sem is available (see `leyline:sem-integration`),\nalso run `sem diff --format plain --staged` to display an entity-level\nsummary alongside the stat output. This shows which\nfunctions, classes, and methods changed rather than just\nline counts.\n\n## Step 5: Review Detailed Diff (`diff-details`)\n\nRun `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.\n\n## Exit Criteria\n\nComplete 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.\n\n## Supporting Modules\n\n- [Git commands reference](modules/git-commands.md) - diff, status, branch operations for sanctum workflows\n\n## Troubleshooting\n\nIf 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.\n\nFile v1.0.3:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-sanctum-git-workspace-review\",\n \"version\": \"1.0.3\",\n \"publishedAt\": 1781796019797\n}\n\nFile v1.0.3:modules/git-commands.md\n\n---\nparent_skill: sanctum:shared\nname: git-commands\ndescription: Common git commands used across sanctum workflows\ncategory: patterns\ntags: [git, commands, diff, status]\nestimated_tokens: 200\n---\n\n# Git Commands for Sanctum Workflows\n\n## Repository Confirmation\n\n### Verify Working Directory\n```bash\npwd\n```\nvalidates you are in the correct repository before running git operations.\n\n### Check Branch and Status\n```bash\ngit status -sb\n```\nShows current branch, upstream tracking, and short status in one line.\n\n## Diff Commands\n\n### Staged Changes Statistics\n```bash\ngit diff --cached --stat\n```\nShows file-by-file statistics for staged changes (insertions/deletions).\n\n### Staged Changes Details\n```bash\ngit diff --cached\n```\nFull diff of staged changes for review before commit.\n\n### Unstaged Changes Statistics\n```bash\ngit diff --stat\n```\nFile-by-file statistics for unstaged working directory changes.\n\n### Unstaged Changes Details\n```bash\ngit diff\n```\nFull diff of unstaged working directory changes.\n\n### Branch Comparison Statistics\n```bash\ngit diff --stat origin/main...HEAD\n```\nShows statistics for all commits in current branch since diverging from main.\n\n### Branch Comparison Details\n```bash\ngit diff origin/main...HEAD\n```\nFull diff of all changes in current branch compared to main.\n\n## Status Parsing Patterns\n\n### Extract Branch Name\nFrom `git status -sb` output, the first line shows:\n```\n## branch-name...origin/branch-name [ahead N, behind M]\n```\n\nParse the branch name from the `##` line.\n\n### Identify Staged vs Unstaged\n- Lines starting with `M ` (M-space): staged modification\n- Lines starting with ` M` (space-M): unstaged modification\n- Lines starting with `A ` (A-space): staged new file\n- Lines starting with `??`: untracked file\n\n### Count Changes\nUse `--stat` output to count affected files:\n```\n file1.md | 10 +++++++---\n file2.py | 5 +++++\n 2 files changed, 12 insertions(+), 3 deletions(-)\n```\n\n## Branch Operations\n\n### Get Merge Base\n```bash\ngit merge-base origin/main HEAD\n```\nFinds the common ancestor commit for comparison.\n\n### List Recent Commits\n```bash\ngit log --oneline -10\n```\nShows last 10 commits in compact format.\n\n### Show Commit Details\n```bash\ngit show \n```\nDisplays commit message and diff for a specific commit.\n\n## Best Practices\n\n### Always Run in Sequence\n1. `pwd` - Confirm location\n2. `git status -sb` - Check branch/status\n3. `git diff --cached --stat` - Review staged stats\n4. `git diff --cached` - Review staged details\n\n### Use Limits\n- Always limit `git log` output (e.g., `-10`, `-20`)\n- Use `--stat` before full diffs to understand scope\n- For large diffs, consider `git diff --cached -- `\n\n### Error Handling\n- Check if `git status` shows \"Not a git repository\"\n- Verify upstream tracking exists before comparing to origin\n- Handle empty diffs (no staged changes) gracefully\n\nFile v1.0.3:skill-card.md\n\n## Description:
\nVerifies workspace state and staged changes as a preflight before commits, pull requests, or release notes.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[athola](https://clawhub.ai/user/athola)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and release maintainers use this skill to review repository status, staged and unstaged diffs, and project quality checks before running workflows that depend on a clean intended change set.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The release evidence reports that this skill is framed as read-only review but can change repository state and run project-defined commands.
\nMitigation: Install only when active git staging and formatting or lint workflows are desired, and require explicit confirmation before staging, unstaging, formatting, fixing, or aborting merge state.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/athola/nm-sanctum-git-workspace-review)
\n- [Sanctum source homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum)
\n\n\n## Skill Output:
\n**Output Type(s):** [Analysis, Shell commands, Guidance]
\n**Output Format:** [Markdown with inline shell commands and status summaries]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May include repository status, diff statistics, detailed diff observations, and suggested follow-up checks.]
\n\n## Skill Version(s):
\n1.0.3 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.2: 4 files, 4451 bytes\n\nFiles: modules/git-commands.md (2868b), skill-card.md (1878b), SKILL.md (3651b), _meta.json (150b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: git-workspace-review\ndescription: |\n Verify workspace state, staged changes, and preflight checks before commits or PRs\nversion: 1.9.5\ntriggers:\n - git\n - preflight\n - status\n - diff\n - staged\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# Git Workspace Review\n\n## Table of Contents\n\n1. [Usage](#usage)\n2. [Required Progress Tracking](#required-progress-tracking)\n\n## Verification\n\nRun `git status` after review to verify workspace state matches expectations.\n\n## Testing\n\nRun `pytest plugins/sanctum/tests/test_git_workspace_review.py` to validate review workflow.\n\n## Usage\n\nUse 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.\n\n## Required Progress Tracking\n\n1. `git-review:repo-confirmed`\n2. `git-review:status-overview`\n3. `git-review:code-quality-check`\n4. `git-review:diff-stat`\n5. `git-review:diff-details`\n\nMark each item as complete as you finish the corresponding step.\n\n## Step 1: Confirm Repository (`repo-confirmed`)\n\nRun `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.\n\n## Step 2: Review Status Overview (`status-overview`)\n\nAnalyze the `git status -sb` output for staged and unstaged changes. Stage or unstage files so that subsequent workflows operate on the intended diff.\n\n## Step 3: Check Code Quality (`code-quality-check`)\n\nRun `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.\n\n## Step 4: Review Diff Statistics (`diff-stat`)\n\nRun `git diff --cached --stat` for staged changes (or\n`git diff --stat` for unstaged work). Note the number of\nfiles modified and identify hotspots with large insertion\nor deletion counts.\n\nWhen sem is available (see `leyline:sem-integration`),\nalso run `sem diff --staged` to display an entity-level\nsummary alongside the stat output. This shows which\nfunctions, classes, and methods changed rather than just\nline counts.\n\n## Step 5: Review Detailed Diff (`diff-details`)\n\nRun `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.\n\n## Exit Criteria\n\nComplete 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.\n\n## Supporting Modules\n\n- [Git commands reference](modules/git-commands.md) - diff, status, branch operations for sanctum workflows\n\n## Troubleshooting\n\nIf 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.\n\nFile v1.0.2:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-sanctum-git-workspace-review\",\n \"version\": \"1.0.2\",\n \"publishedAt\": 1778293192286\n}\n\nFile v1.0.2:modules/git-commands.md\n\n---\nparent_skill: sanctum:shared\nname: git-commands\ndescription: Common git commands used across sanctum workflows\ncategory: patterns\ntags: [git, commands, diff, status]\nestimated_tokens: 200\n---\n\n# Git Commands for Sanctum Workflows\n\n## Repository Confirmation\n\n### Verify Working Directory\n```bash\npwd\n```\nvalidates you are in the correct repository before running git operations.\n\n### Check Branch and Status\n```bash\ngit status -sb\n```\nShows current branch, upstream tracking, and short status in one line.\n\n## Diff Commands\n\n### Staged Changes Statistics\n```bash\ngit diff --cached --stat\n```\nShows file-by-file statistics for staged changes (insertions/deletions).\n\n### Staged Changes Details\n```bash\ngit diff --cached\n```\nFull diff of staged changes for review before commit.\n\n### Unstaged Changes Statistics\n```bash\ngit diff --stat\n```\nFile-by-file statistics for unstaged working directory changes.\n\n### Unstaged Changes Details\n```bash\ngit diff\n```\nFull diff of unstaged working directory changes.\n\n### Branch Comparison Statistics\n```bash\ngit diff --stat origin/main...HEAD\n```\nShows statistics for all commits in current branch since diverging from main.\n\n### Branch Comparison Details\n```bash\ngit diff origin/main...HEAD\n```\nFull diff of all changes in current branch compared to main.\n\n## Status Parsing Patterns\n\n### Extract Branch Name\nFrom `git status -sb` output, the first line shows:\n```\n## branch-name...origin/branch-name [ahead N, behind M]\n```\n\nParse the branch name from the `##` line.\n\n### Identify Staged vs Unstaged\n- Lines starting with `M ` (M-space): staged modification\n- Lines starting with ` M` (space-M): unstaged modification\n- Lines starting with `A ` (A-space): staged new file\n- Lines starting with `??`: untracked file\n\n### Count Changes\nUse `--stat` output to count affected files:\n```\n file1.md | 10 +++++++---\n file2.py | 5 +++++\n 2 files changed, 12 insertions(+), 3 deletions(-)\n```\n\n## Branch Operations\n\n### Get Merge Base\n```bash\ngit merge-base origin/main HEAD\n```\nFinds the common ancestor commit for comparison.\n\n### List Recent Commits\n```bash\ngit log --oneline -10\n```\nShows last 10 commits in compact format.\n\n### Show Commit Details\n```bash\ngit show \n```\nDisplays commit message and diff for a specific commit.\n\n## Best Practices\n\n### Always Run in Sequence\n1. `pwd` - Confirm location\n2. `git status -sb` - Check branch/status\n3. `git diff --cached --stat` - Review staged stats\n4. `git diff --cached` - Review staged details\n\n### Use Limits\n- Always limit `git log` output (e.g., `-10`, `-20`)\n- Use `--stat` before full diffs to understand scope\n- For large diffs, consider `git diff --cached -- `\n\n### Error Handling\n- Check if `git status` shows \"Not a git repository\"\n- Verify upstream tracking exists before comparing to origin\n- Handle empty diffs (no staged changes) gracefully\n\nFile v1.0.2:skill-card.md\n\n## Description:
\nVerify workspace state, staged changes, and preflight checks before commits or PRs.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[athola](https://clawhub.ai/user/athola)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and engineers use this skill to review repository status, staged or unstaged diffs, and pre-commit checks before commits, pull requests, or release notes.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Project Makefile targets may execute local formatting or linting commands.
\nMitigation: Use the skill in repositories you trust and review command intent before execution.
\nRisk: Staging or unstaging files can change the intended commit contents.
\nMitigation: Review git status and diffs before committing or handing the workspace to downstream workflows.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/athola/nm-sanctum-git-workspace-review)
\n- [Project homepage from ClawHub metadata](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum)
\n\n\n## Skill Output:
\n**Output Type(s):** [guidance, shell commands, markdown]
\n**Output Format:** [Markdown guidance with inline shell commands and checklist steps]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Produces review steps for local Git status, diff statistics, detailed diffs, and preflight checks.]
\n\n## Skill Version(s):
\n1.0.2 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.1: 3 files, 3431 bytes\n\nFiles: modules/git-commands.md (2868b), SKILL.md (3651b), _meta.json (150b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: git-workspace-review\ndescription: |\n Verify workspace state, staged changes, and preflight checks before commits or PRs\nversion: 1.9.4\ntriggers:\n - git\n - preflight\n - status\n - diff\n - staged\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# Git Workspace Review\n\n## Table of Contents\n\n1. [Usage](#usage)\n2. [Required Progress Tracking](#required-progress-tracking)\n\n## Verification\n\nRun `git status` after review to verify workspace state matches expectations.\n\n## Testing\n\nRun `pytest plugins/sanctum/tests/test_git_workspace_review.py` to validate review workflow.\n\n## Usage\n\nUse 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.\n\n## Required Progress Tracking\n\n1. `git-review:repo-confirmed`\n2. `git-review:status-overview`\n3. `git-review:code-quality-check`\n4. `git-review:diff-stat`\n5. `git-review:diff-details`\n\nMark each item as complete as you finish the corresponding step.\n\n## Step 1: Confirm Repository (`repo-confirmed`)\n\nRun `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.\n\n## Step 2: Review Status Overview (`status-overview`)\n\nAnalyze the `git status -sb` output for staged and unstaged changes. Stage or unstage files so that subsequent workflows operate on the intended diff.\n\n## Step 3: Check Code Quality (`code-quality-check`)\n\nRun `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.\n\n## Step 4: Review Diff Statistics (`diff-stat`)\n\nRun `git diff --cached --stat` for staged changes (or\n`git diff --stat` for unstaged work). Note the number of\nfiles modified and identify hotspots with large insertion\nor deletion counts.\n\nWhen sem is available (see `leyline:sem-integration`),\nalso run `sem diff --staged` to display an entity-level\nsummary alongside the stat output. This shows which\nfunctions, classes, and methods changed rather than just\nline counts.\n\n## Step 5: Review Detailed Diff (`diff-details`)\n\nRun `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.\n\n## Exit Criteria\n\nComplete 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.\n\n## Supporting Modules\n\n- [Git commands reference](modules/git-commands.md) - diff, status, branch operations for sanctum workflows\n\n## Troubleshooting\n\nIf 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.\n\nFile v1.0.1:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-sanctum-git-workspace-review\",\n \"version\": \"1.0.1\",\n \"publishedAt\": 1778077275344\n}\n\nFile v1.0.1:modules/git-commands.md\n\n---\nparent_skill: sanctum:shared\nname: git-commands\ndescription: Common git commands used across sanctum workflows\ncategory: patterns\ntags: [git, commands, diff, status]\nestimated_tokens: 200\n---\n\n# Git Commands for Sanctum Workflows\n\n## Repository Confirmation\n\n### Verify Working Directory\n```bash\npwd\n```\nvalidates you are in the correct repository before running git operations.\n\n### Check Branch and Status\n```bash\ngit status -sb\n```\nShows current branch, upstream tracking, and short status in one line.\n\n## Diff Commands\n\n### Staged Changes Statistics\n```bash\ngit diff --cached --stat\n```\nShows file-by-file statistics for staged changes (insertions/deletions).\n\n### Staged Changes Details\n```bash\ngit diff --cached\n```\nFull diff of staged changes for review before commit.\n\n### Unstaged Changes Statistics\n```bash\ngit diff --stat\n```\nFile-by-file statistics for unstaged working directory changes.\n\n### Unstaged Changes Details\n```bash\ngit diff\n```\nFull diff of unstaged working directory changes.\n\n### Branch Comparison Statistics\n```bash\ngit diff --stat origin/main...HEAD\n```\nShows statistics for all commits in current branch since diverging from main.\n\n### Branch Comparison Details\n```bash\ngit diff origin/main...HEAD\n```\nFull diff of all changes in current branch compared to main.\n\n## Status Parsing Patterns\n\n### Extract Branch Name\nFrom `git status -sb` output, the first line shows:\n```\n## branch-name...origin/branch-name [ahead N, behind M]\n```\n\nParse the branch name from the `##` line.\n\n### Identify Staged vs Unstaged\n- Lines starting with `M ` (M-space): staged modification\n- Lines starting with ` M` (space-M): unstaged modification\n- Lines starting with `A ` (A-space): staged new file\n- Lines starting with `??`: untracked file\n\n### Count Changes\nUse `--stat` output to count affected files:\n```\n file1.md | 10 +++++++---\n file2.py | 5 +++++\n 2 files changed, 12 insertions(+), 3 deletions(-)\n```\n\n## Branch Operations\n\n### Get Merge Base\n```bash\ngit merge-base origin/main HEAD\n```\nFinds the common ancestor commit for comparison.\n\n### List Recent Commits\n```bash\ngit log --oneline -10\n```\nShows last 10 commits in compact format.\n\n### Show Commit Details\n```bash\ngit show \n```\nDisplays commit message and diff for a specific commit.\n\n## Best Practices\n\n### Always Run in Sequence\n1. `pwd` - Confirm location\n2. `git status -sb` - Check branch/status\n3. `git diff --cached --stat` - Review staged stats\n4. `git diff --cached` - Review staged details\n\n### Use Limits\n- Always limit `git log` output (e.g., `-10`, `-20`)\n- Use `--stat` before full diffs to understand scope\n- For large diffs, consider `git diff --cached -- `\n\n### Error Handling\n- Check if `git status` shows \"Not a git repository\"\n- Verify upstream tracking exists before comparing to origin\n- Handle empty diffs (no staged changes) gracefully\n\nArchive v1.0.0: 3 files, 3430 bytes\n\nFiles: modules/git-commands.md (2868b), SKILL.md (3651b), _meta.json (150b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: git-workspace-review\ndescription: |\n Verify workspace state, staged changes, and preflight checks before commits or PRs\nversion: 1.8.2\ntriggers:\n - git\n - preflight\n - status\n - diff\n - staged\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# Git Workspace Review\n\n## Table of Contents\n\n1. [Usage](#usage)\n2. [Required Progress Tracking](#required-progress-tracking)\n\n## Verification\n\nRun `git status` after review to verify workspace state matches expectations.\n\n## Testing\n\nRun `pytest plugins/sanctum/tests/test_git_workspace_review.py` to validate review workflow.\n\n## Usage\n\nUse 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.\n\n## Required Progress Tracking\n\n1. `git-review:repo-confirmed`\n2. `git-review:status-overview`\n3. `git-review:code-quality-check`\n4. `git-review:diff-stat`\n5. `git-review:diff-details`\n\nMark each item as complete as you finish the corresponding step.\n\n## Step 1: Confirm Repository (`repo-confirmed`)\n\nRun `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.\n\n## Step 2: Review Status Overview (`status-overview`)\n\nAnalyze the `git status -sb` output for staged and unstaged changes. Stage or unstage files so that subsequent workflows operate on the intended diff.\n\n## Step 3: Check Code Quality (`code-quality-check`)\n\nRun `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.\n\n## Step 4: Review Diff Statistics (`diff-stat`)\n\nRun `git diff --cached --stat` for staged changes (or\n`git diff --stat` for unstaged work). Note the number of\nfiles modified and identify hotspots with large insertion\nor deletion counts.\n\nWhen sem is available (see `leyline:sem-integration`),\nalso run `sem diff --staged` to display an entity-level\nsummary alongside the stat output. This shows which\nfunctions, classes, and methods changed rather than just\nline counts.\n\n## Step 5: Review Detailed Diff (`diff-details`)\n\nRun `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.\n\n## Exit Criteria\n\nComplete 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.\n\n## Supporting Modules\n\n- [Git commands reference](modules/git-commands.md) - diff, status, branch operations for sanctum workflows\n\n## Troubleshooting\n\nIf 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.\n\nFile v1.0.0:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-sanctum-git-workspace-review\",\n \"version\": \"1.0.0\",\n \"publishedAt\": 1776279708112\n}\n\nFile v1.0.0:modules/git-commands.md\n\n---\nparent_skill: sanctum:shared\nname: git-commands\ndescription: Common git commands used across sanctum workflows\ncategory: patterns\ntags: [git, commands, diff, status]\nestimated_tokens: 200\n---\n\n# Git Commands for Sanctum Workflows\n\n## Repository Confirmation\n\n### Verify Working Directory\n```bash\npwd\n```\nvalidates you are in the correct repository before running git operations.\n\n### Check Branch and Status\n```bash\ngit status -sb\n```\nShows current branch, upstream tracking, and short status in one line.\n\n## Diff Commands\n\n### Staged Changes Statistics\n```bash\ngit diff --cached --stat\n```\nShows file-by-file statistics for staged changes (insertions/deletions).\n\n### Staged Changes Details\n```bash\ngit diff --cached\n```\nFull diff of staged changes for review before commit.\n\n### Unstaged Changes Statistics\n```bash\ngit diff --stat\n```\nFile-by-file statistics for unstaged working directory changes.\n\n### Unstaged Changes Details\n```bash\ngit diff\n```\nFull diff of unstaged working directory changes.\n\n### Branch Comparison Statistics\n```bash\ngit diff --stat origin/main...HEAD\n```\nShows statistics for all commits in current branch since diverging from main.\n\n### Branch Comparison Details\n```bash\ngit diff origin/main...HEAD\n```\nFull diff of all changes in current branch compared to main.\n\n## Status Parsing Patterns\n\n### Extract Branch Name\nFrom `git status -sb` output, the first line shows:\n```\n## branch-name...origin/branch-name [ahead N, behind M]\n```\n\nParse the branch name from the `##` line.\n\n### Identify Staged vs Unstaged\n- Lines starting with `M ` (M-space): staged modification\n- Lines starting with ` M` (space-M): unstaged modification\n- Lines starting with `A ` (A-space): staged new file\n- Lines starting with `??`: untracked file\n\n### Count Changes\nUse `--stat` output to count affected files:\n```\n file1.md | 10 +++++++---\n file2.py | 5 +++++\n 2 files changed, 12 insertions(+), 3 deletions(-)\n```\n\n## Branch Operations\n\n### Get Merge Base\n```bash\ngit merge-base origin/main HEAD\n```\nFinds the common ancestor commit for comparison.\n\n### List Recent Commits\n```bash\ngit log --oneline -10\n```\nShows last 10 commits in compact format.\n\n### Show Commit Details\n```bash\ngit show \n```\nDisplays commit message and diff for a specific commit.\n\n## Best Practices\n\n### Always Run in Sequence\n1. `pwd` - Confirm location\n2. `git status -sb` - Check branch/status\n3. `git diff --cached --stat` - Review staged stats\n4. `git diff --cached` - Review staged details\n\n### Use Limits\n- Always limit `git log` output (e.g., `-10`, `-20`)\n- Use `--stat` before full diffs to understand scope\n- For large diffs, consider `git diff --cached -- `\n\n### Error Handling\n- Check if `git status` shows \"Not a git repository\"\n- Verify upstream tracking exists before comparing to origin\n- Handle empty diffs (no staged changes) gracefully","readmeExcerpt":"Skill: git-workspace-review Owner: athola Summary: Verifies workspace state and staged changes as a read-only preflight. Use before commits or PRs to confirm staged set is clean and correct Tags: latest:1.9.19 Version history: v1.9.19 | 2026-08-26T13:20:25.943Z | user Release v1.9.19 v1.9.17 | 2026-07-30T05:40:29.966Z | user Release v1.9.17 v1.9.16 | 2026-07-14T19:57:24.609Z | user Release v1.9.16 v1.9.14 | 2026-06-3","codeSnippets":[],"executableExamples":[{"language":"bash","snippet":"pwd"},{"language":"bash","snippet":"git status -sb"},{"language":"bash","snippet":"git diff --cached --stat"},{"language":"bash","snippet":"git diff --cached"},{"language":"bash","snippet":"git diff --stat"},{"language":"bash","snippet":"git diff"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: git-workspace-review\ndescription: |\n Verifies workspace state and staged changes as a read-only preflight. Use before commits or PRs to confirm staged set is clean and correct\nversion: 1.9.8\ntriggers:\n - git\n - preflight\n - status\n - diff\n - staged\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# Git Workspace Review\n\n## Table of Contents\n\n1. [Usage](#usage)\n2. [Required Progress Tracking](#required-progress-tracking)\n\n## Verification\n\nRun `git status` after review to verify workspace state matches expectations.\n\n## Testing\n\nRun `pytest plugins/sanctum/tests/test_git_workspace_review.py` to validate review workflow.\n\n## Usage\n\nUse 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.\n\n## Required Progress Tracking\n\n1. `git-review:repo-confirmed`\n2. `git-review:status-overview`\n3. `git-review:code-quality-check`\n4. `git-review:diff-stat`\n5. `git-review:diff-details`\n\nMark each item as complete as you finish the corresponding step.\n\n## Step 1: Confirm Repository (`repo-confirmed`)\n\nRun `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.\n\n## Step 2: Review Status Overview (`status-overview`)\n\nAnalyze the `git status -sb` output for staged and unstaged changes. Stage or unstage files so that subsequent workflows operate on the intended diff.\n\n## Step 3: Check Code Quality (`code-quality-check`)\n\nRun `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.\n\n## Step 4: Review Diff Statistics (`diff-stat`)\n\nRun `git diff --cached --stat` for staged changes (or\n`git diff --stat` for unstaged work). Note the number of\nfiles modified and identify hotspots with large insertion\nor deletion counts.\n\nWhen sem is available (see `leyline:sem-integration`),\nalso run `sem diff --format plain --staged` to display an entity-level\nsummary alongside the stat output. This shows which\nfunctions, classes, and methods changed rather than just\nline counts.\n\n## Step 5: Review Detailed Diff (`diff-details`)\n\nRun `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 f"},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-sanctum-git-workspace-review\",\n \"version\": \"1.9.19\",\n \"publishedAt\": 1787750425943\n}"},{"path":"modules/git-commands.md","content":"---\nparent_skill: sanctum:shared\nname: git-commands\ndescription: Common git commands used across sanctum workflows\ncategory: patterns\ntags: [git, commands, diff, status]\nestimated_tokens: 200\n---\n\n# Git Commands for Sanctum Workflows\n\n## Repository Confirmation\n\n### Verify Working Directory\n```bash\npwd\n```\nvalidates you are in the correct repository before running git operations.\n\n### Check Branch and Status\n```bash\ngit status -sb\n```\nShows current branch, upstream tracking, and short status in one line.\n\n## Diff Commands\n\n### Staged Changes Statistics\n```bash\ngit diff --cached --stat\n```\nShows file-by-file statistics for staged changes (insertions/deletions).\n\n### Staged Changes Details\n```bash\ngit diff --cached\n```\nFull diff of staged changes for review before commit.\n\n### Unstaged Changes Statistics\n```bash\ngit diff --stat\n```\nFile-by-file statistics for unstaged working directory changes.\n\n### Unstaged Changes Details\n```bash\ngit diff\n```\nFull diff of unstaged working directory changes.\n\n### Branch Comparison Statistics\n```bash\ngit diff --stat origin/main...HEAD\n```\nShows statistics for all commits in current branch since diverging from main.\n\n### Branch Comparison Details\n```bash\ngit diff origin/main...HEAD\n```\nFull diff of all changes in current branch compared to main.\n\n## Status Parsing Patterns\n\n### Extract Branch Name\nFrom `git status -sb` output, the first line shows:\n```\n## branch-name...origin/branch-name [ahead N, behind M]\n```\n\nParse the branch name from the `##` line.\n\n### Identify Staged vs Unstaged\n- Lines starting with `M ` (M-space): staged modification\n- Lines starting with ` M` (space-M): unstaged modification\n- Lines starting with `A ` (A-space): staged new file\n- Lines starting with `??`: untracked file\n\n### Count Changes\nUse `--stat` output to count affected files:\n```\n file1.md | 10 +++++++---\n file2.py | 5 +++++\n 2 files changed, 12 insertions(+), 3 deletions(-)\n```\n\n## Branch Operations\n\n### Get Merge Base\n```bash\ngit merge-base origin/main HEAD\n```\nFinds the common ancestor commit for comparison.\n\n### List Recent Commits\n```bash\ngit log --oneline -10\n```\nShows last 10 commits in compact format.\n\n### Show Commit Details\n```bash\ngit show \n```\nDisplays commit message and diff for a specific commit.\n\n## Best Practices\n\n### Always Run in Sequence\n1. `pwd` - Confirm location\n2. `git status -sb` - Check branch/status\n3. `git diff --cached --stat` - Review staged stats\n4. `git diff --cached` - Review staged details\n\n### Use Limits\n- Always limit `git log` output (e.g., `-10`, `-20`)\n- Use `--stat` before full diffs to understand scope\n- For large diffs, consider `git diff --cached -- `\n\n### Error Handling\n- Check if `git status` shows \"Not a git repository\"\n- Verify upstream tracking exists before comparing to origin\n- Handle empty diffs (no staged changes) gracefully"},{"path":"skill-card.md","content":"## Description:\n\nVerifies workspace state and staged changes as a read-only preflight before commits or PRs.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[athola](https://clawhub.ai/user/athola)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and engineers use this skill to inspect repository status, staged changes, and diffs before commit, PR, or release-note workflows. It helps confirm that the intended files are staged and that code-quality checks have been considered.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill is described as read-only, but evidence.security reports that following it may run Makefile targets, stage or unstage files, and format code.\n\nMitigation: Use only in trusted repositories and require explicit confirmation before commands that change files, change the Git index, or execute project-defined targets.\n\nRisk: Repository-defined quality checks such as make format and make lint can execute local project code or change formatting.\n\nMitigation: Review the relevant Makefile targets before execution and prefer a clean working tree or disposable branch when testing unfamiliar repositories.\n\n## Reference(s):\n\n- [Project homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, guidance]\n\n**Output Format:** [Markdown guidance with inline shell commands]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May prompt the agent to run repository-defined commands and modify the Git index or files when following the workflow.]\n\n## Skill Version(s):\n\n1.9.19 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":null,"editorialQuality":{"score":100,"threshold":65,"status":"thin","wordCount":1440,"uniquenessScore":43,"reasons":["uniqueness-below-45"]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-10T08:59:54.068Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-10T08:59:54.068Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-10T11:54:03.151Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}