git-claw

---

A consistent Git history that's easy to read: for both humans and agents.

git-claw is an Agent Skill that keeps your commits, PRs, issues, and code reviews in a unified format. Install once, and every collaboration artifact follows the same conventions: whether you're working solo or in a team.

• Readable history: Structured commits, PRs, and issues that anyone (or any agent) can follow at a glance
• Multi-model code review: Domain agents, plus optional Codex adversarial analysis, cross-validated and severity-ranked
• Session continuity: /handoff captures work context so the next session picks up where you left off

---

Skills

	Skill	What it does
📝	/commit	Conventional commits from your diff
🔀	/pr	Structured PRs with auto-labeling
📋	/issue	Templated issues with priority labels
💬	/review-reply	Analyze and reply to review comments
🔍	/code-review	Multi-agent severity-based code review
🤝	/handoff	Session transfer prompt generation
📖	/explain-diff	Interactive HTML explainer for understanding a diff
🧪	/micro-world	Throwaway interactive simulation of a behavior
📄	/visual-doc	On-brand interactive document from researched/analyzed content
🖼️	/eli5	Picture-first explainer for someone outside the domain

Installation

Claude Code Plugin (Recommended)

# Add marketplace
/plugin marketplace add chanmuzi/git-claw

# Install plugin
/plugin install git-claw@git-claw

Skills CLI

npx skills add chanmuzi/git-claw

The interactive installer lets you select skills, target agents, scope (project/global), and install method.

npx skills add chanmuzi/git-claw --skill commit --skill pr --skill issue --skill review-reply --skill code-review --skill handoff --skill explain-diff --skill micro-world --skill visual-doc --skill eli5 -g

Update

Claude Code Plugin:

/plugin update git-claw@git-claw

Or enable auto-update: /plugin → Marketplaces tab → select marketplace → Enable auto-update

Skills CLI:

npx skills check    # Check for updates
npx skills update   # Update all installed skills

Symlink installs (recommended) apply updates to all agents at once. Copy installs require updating each copy individually.

Skill renames are not auto-tracked. When a skill is renamed upstream, the Skills CLI keeps the old folder around, so you may see two skills with the same description, or the skill may surface under its old name. Remove the stale folder manually: match the scope you installed with:

# Global install (npx skills add ... -g)  →  ~/.codex/skills/{old-name}
npx skills remove {old-name} -g     # or
rm -rf ~/.codex/skills/{old-name}

# Project install (npx skills add ... without -g)  →  ./.codex/skills/{old-name}
npx skills remove {old-name}        # or
rm -rf ./.codex/skills/{old-name}

Then restart your Codex CLI session so the skill list is re-cached.

Skills

Skill prefix by agent: Claude Code uses / (e.g., /commit), Codex CLI uses $ (e.g., $commit).

/commit: Create a Git Commit

Analyzes your staged/unstaged changes and proposes conventional commit messages. Before staging, files are grouped by intent (infrastructure, agent config, app code, build tooling, docs, tests), and multi-intent changes are automatically split into separate commits with same-intent exceptions for tightly coupled changes (schema+code, signature+call-sites, code+validating tests). Messages never use the em-dash, the en-dash, or the middle dot.

/commit              # Analyze and commit
/commit --amend      # Amend the last commit

Types: feat, fix, refactor, style, docs, test, perf, chore, hotfix

/pr: Create a Pull Request

Creates a PR with a structured template. Automatically detects Individual or Release mode. Titles and bodies never use the em-dash, the en-dash, or the middle dot, the usual markers of machine-written text; every skill follows the same rule.

/pr              # Individual PR (Feat, Fix, Refactor, etc.)
/pr -g           # Include Mermaid change-flow graph
/pr release      # Release PR (dev → main integration)

After creating an individual PR, the skill offers a one-line opt-in to generate an /explain-diff explainer for the change (default No, never re-asked).

/issue: Create a GitHub Issue

Creates a structured issue with the appropriate template and auto-assigns type/priority labels.

/issue             # General issue (type inferred from context)
/issue bug         # Bug report
/issue feature     # Feature request

/review-reply: Review & Reply to PR Comments

Collects review comments (CodeRabbit, Copilot, teammates, etc.) from a PR, analyzes their validity against the actual code, and discusses findings with you. Each item quotes the source verbatim and shows the proposed change as a diff, so you can accept or reject a suggestion without opening the files yourself: including dismissals, which quote the code that refutes the reviewer.

/review-reply          # Review current branch's PR
/review-reply 42       # Review PR #42

This is the beginning of the README. Read the rest at the original. Read the full README ↗