git

A command set for working with Git, the version-control system that records code changes and manages branches. It can check repository state, create commits, push and pull changes, and manage merges.

In plain words
What is it for?
Use it to inspect a repository, add and commit files, synchronize with remote repositories, create or manage branches, generate commit messages, and work through merge conflicts.
Why use it?
It reduces the manual work of checking changes, choosing Git commands, writing commit messages, and following consistent branch practices. It also provides guidance when merges have conflicts.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/superclaude-org/superclaude_plugin/sc-git
Clone the repo
git clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_Plugin
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 506 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 97% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00011 $0.00506
Opus 5 $0.00005 $0.00253
Sonnet 5 $0.00002 $0.00101
Haiku 4.5 $0.00001 $0.00051

Measured 2d ago against content hash 4e6d92aac61a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

git scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

97% identical to git — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

commands/sc-git.md · 80 lines

How it starts

The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/sc:sc:sc:git - Git Operations

Triggers

  • Git repository operations: status, add, commit, push, pull, branch
  • Need for intelligent commit message generation
  • Repository workflow optimization requests
  • Branch management and merge operations

Usage

/sc:sc:git [operation] [args] [--smart-commit] [--interactive]

Behavioral Flow

  1. Analyze: Check repository state and working directory changes
  2. Validate: Ensure operation is appropriate for current Git context
  3. Execute: Run Git command with intelligent automation
  4. Optimize: Apply smart commit messages and workflow patterns
  5. Report: Provide status and next steps guidance

Key behaviors:

  • Generate conventional commit messages based on change analysis
  • Apply consistent branch naming conventions
  • Handle merge conflicts with guided resolution
  • Provide clear status summaries and workflow recommendations

Tool Coordination

  • Bash: Git command execution and repository operations
  • Read: Repository state analysis and configuration review
  • Grep: Log parsing and status analysis
  • Write: Commit message generation and documentation

Key Patterns

  • Smart Commits: Analyze changes → generate conventional commit message
  • Status Analysis: Repository state → actionable recommendations
  • Branch Strategy: Consistent naming and workflow enforcement
  • Error Recovery: Conflict resolution and state restoration guidance

Examples

Smart Status Analysis

/sc:sc:git status
# Analyzes repository state with change summary
# Provides next steps and workflow recommendations

Intelligent Commit

/sc:sc:git commit --smart-commit
# Generates conventional commit message from change analysis
# Applies best practices and consistent formatting

Interactive Operations

/sc:sc:git merge feature-branch --interactive
# Guided merge with conflict resolution assistance

Boundaries

Will:

  • Execute Git operations with intelligent automation
  • Generate conventional commit messages from change analysis
  • Provide workflow optimization and best practice guidance

Read the full file on GitHub · 80 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 80 lines · 11 tokens per session scan A 4e6d92aac61a

Subscribe to this mod's changes

git is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Plugin (55 stars, last pushed 12d ago), licensed MIT. It adds 11 tokens to every session and 506 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to git, differing in 10 lines, and is treated as a copy.