What makes git-workspace-review notable?

1.5K downloads. Trust evidence available

How should git-workspace-review be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

git-workspace-review

Verifies workspace state and staged changes as a read-only preflight. Use before commits or PRs to confirm staged set is clean and correct

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.5k

Updated

Oct 10, 2026

Version

1.9.19

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.5K downloads reported by the source. Last updated 10/10/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 10, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 10, 2026
Adoption signal: 1.5K downloadsadoption · observed Oct 10, 2026
Latest release: 1.9.19release · observed Aug 26, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17emme0e2m3cpf7k2jvp3a84984b8z9:nm-sanctum-git-workspace-review

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: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-git-workspace-review/snapshot"

Documentation

CLAWHUB

87,192 characters of source documentation, loaded on request.

Extracted files

4 files captured from the source.

SKILL.md

---
name: git-workspace-review
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
version: 1.9.8
triggers:
- git
- preflight
- status
- diff
- staged
metadata: {"openclaw": {"homepage": "https://github.com/athola/claude-night-market/tree/master/plugins/sanctum", "emoji": "\ud83e\udd9e", "requires": {"config": ["night-market.sanctum:shared"]}}}
source: claude-night-market
source_plugin: sanctum
---

> **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.

# Git Workspace Review

## Table of Contents

1. [Usage](#usage)
2. [Required Progress Tracking](#required-progress-tracking)

## Verification

Run `git status` after review to verify workspace state matches expectations.

## Testing

Run `pytest plugins/sanctum/tests/test_git_workspace_review.py` to validate review workflow.

## Usage

Use this skill before workflows that depend on repository state, such as commit message generation, PR preparation, or release notes. Run it once per session or whenever staged changes are modified.

## Required Progress Tracking

1. `git-review:repo-confirmed`
2. `git-review:status-overview`
3. `git-review:code-quality-check`
4. `git-review:diff-stat`
5. `git-review:diff-details`

Mark each item as complete as you finish the corresponding step.

## Step 1: Confirm Repository (`repo-confirmed`)

Run `pwd` to confirm you are in the correct repository directory. Execute `git status -sb` to view the current branch and short status, then capture the branch name and upstream information.

## Step 2: Review Status Overview (`status-overview`)

Analyze the `git status -sb` output for staged and unstaged changes. Stage or unstage files so that subsequent workflows operate on the intended diff.

## Step 3: Check Code Quality (`code-quality-check`)

Run `make format && make lint` to validate code quality before committing. Fix any errors immediately. Do not bypass pre-commit hooks with `--no-verify`. This check identifies issues early and avoids late-stage pipeline failures.

## Step 4: Review Diff Statistics (`diff-stat`)

Run `git diff --cached --stat` for staged changes (or
`git diff --stat` for unstaged work). Note the number of
files modified and identify hotspots with large insertion
or deletion counts.

When sem is available (see `leyline:sem-integration`),
also run `sem diff --format plain --staged` to display an entity-level
summary alongside the stat output. This shows which
functions, classes, and methods changed rather than just
line counts.

## Step 5: Review Detailed Diff (`diff-details`)

Run `git diff --cached` to examine the actual changes. For unstaged work, use `git diff`. Identify key themes, such as Makefile adjustments or new skill additions, to provide context f

_meta.json

{
  "ownerId": "kn7d107jg9jv602h9ytsegydq184a42s",
  "slug": "nm-sanctum-git-workspace-review",
  "version": "1.9.19",
  "publishedAt": 1787750425943
}

modules/git-commands.md

---
parent_skill: sanctum:shared
name: git-commands
description: Common git commands used across sanctum workflows
category: patterns
tags: [git, commands, diff, status]
estimated_tokens: 200
---

# Git Commands for Sanctum Workflows

## Repository Confirmation

### Verify Working Directory
```bash
pwd
```
validates you are in the correct repository before running git operations.

### Check Branch and Status
```bash
git status -sb
```
Shows current branch, upstream tracking, and short status in one line.

## Diff Commands

### Staged Changes Statistics
```bash
git diff --cached --stat
```
Shows file-by-file statistics for staged changes (insertions/deletions).

### Staged Changes Details
```bash
git diff --cached
```
Full diff of staged changes for review before commit.

### Unstaged Changes Statistics
```bash
git diff --stat
```
File-by-file statistics for unstaged working directory changes.

### Unstaged Changes Details
```bash
git diff
```
Full diff of unstaged working directory changes.

### Branch Comparison Statistics
```bash
git diff --stat origin/main...HEAD
```
Shows statistics for all commits in current branch since diverging from main.

### Branch Comparison Details
```bash
git diff origin/main...HEAD
```
Full diff of all changes in current branch compared to main.

## Status Parsing Patterns

### Extract Branch Name
From `git status -sb` output, the first line shows:
```
## branch-name...origin/branch-name [ahead N, behind M]
```

Parse the branch name from the `##` line.

### Identify Staged vs Unstaged
- Lines starting with `M ` (M-space): staged modification
- Lines starting with ` M` (space-M): unstaged modification
- Lines starting with `A ` (A-space): staged new file
- Lines starting with `??`: untracked file

### Count Changes
Use `--stat` output to count affected files:
```
 file1.md | 10 +++++++---
 file2.py | 5 +++++
 2 files changed, 12 insertions(+), 3 deletions(-)
```

## Branch Operations

### Get Merge Base
```bash
git merge-base origin/main HEAD
```
Finds the common ancestor commit for comparison.

### List Recent Commits
```bash
git log --oneline -10
```
Shows last 10 commits in compact format.

### Show Commit Details
```bash
git show <commit-hash>
```
Displays commit message and diff for a specific commit.

## Best Practices

### Always Run in Sequence
1. `pwd` - Confirm location
2. `git status -sb` - Check branch/status
3. `git diff --cached --stat` - Review staged stats
4. `git diff --cached` - Review staged details

### Use Limits
- Always limit `git log` output (e.g., `-10`, `-20`)
- Use `--stat` before full diffs to understand scope
- For large diffs, consider `git diff --cached -- <specific-file>`

### Error Handling
- Check if `git status` shows "Not a git repository"
- Verify upstream tracking exists before comparing to origin
- Handle empty diffs (no staged changes) gracefully

skill-card.md

## Description:

Verifies workspace state and staged changes as a read-only preflight before commits or PRs.

This skill is ready for commercial/non-commercial use.

## Publisher:

[athola](https://clawhub.ai/user/athola)

### License/Terms of Use:

MIT-0

## Use Case:

Developers 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.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: 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.

Mitigation: Use only in trusted repositories and require explicit confirmation before commands that change files, change the Git index, or execute project-defined targets.

Risk: Repository-defined quality checks such as make format and make lint can execute local project code or change formatting.

Mitigation: Review the relevant Makefile targets before execution and prefer a clean working tree or disposable branch when testing unfamiliar repositories.

## Reference(s):

- [Project homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum)

## Skill Output:

**Output Type(s):** [text, markdown, shell commands, guidance]

**Output Format:** [Markdown guidance with inline shell commands]

**Output Parameters:** [1D]

**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.]

## Skill Version(s):

1.9.19 (source: server release evidence)

## Ethical Considerations:

Users 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.

Github ReposUpdated 16h agoRank 70

AionUi

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!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

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

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.