Git
- 1 repo stars
- Updated August 4, 2026
- stbenjam/claude-nine
git is an agent skill that guides standard git workflows for branching, commits, and collaboration from the agent.
About
git is a compact agent skill from the claude-nine plugin set that steers your assistant through everyday git workflows while you ship features alone. The published readme is minimal, so treat it as procedural backing for branch, commit, fetch, merge, and pull-request habits rather than a full Git tutorial. developers invoke it when they want the agent to propose safe command sequences, keep history readable, and align with common PR-oriented flows without pasting Stack Overflow snippets. It spans active coding in Build and handoff in Ship when you open or update reviews. Because detail in SKILL.md is thin, pair it with your team’s branch naming rules in repo docs; the skill nudges structure, not policy enforcement. Skip if you already use a heavier git MCP or hosted CI that owns the entire release git graph.
- Git workflow guidance for agent-driven repos
- Supports standard solo-builder version-control rituals during implementation
- Fits Claude Nine plugin stack for terminal-adjacent coding sessions
- Lightweight skill surface when full git UX is not bundled in the agent
Git by the numbers
- Data as of Aug 5, 2026 (Skillselion catalog sync)
/plugin marketplace add stbenjam/claude-nine/plugin install git@claude-nineAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| repo stars | ★ 1 |
|---|---|
| Last updated | August 4, 2026 |
| Repository | stbenjam/claude-nine ↗ |
What it does
Run consistent git workflows—branching, commits, merges, and PR hygiene—with your agent instead of improvising commands.
Who is it for?
Best when you use Claude Nine or similar agents and want lightweight git workflow prompts during daily coding.
Skip if: Skip if you need deep release-train, monorepo, or signed-commit policy automation beyond generic git rituals.
When should I use this skill?
When the user needs git workflow assistance—branching, committing, syncing, or PR-oriented steps—in an agent session.
What you get
After the skill runs, the agent follows a consistent git workflow appropriate to the repo context instead of one-off command guesses.
- Recommended or executed git command sequences
- Branch and commit state aligned to the requested workflow
Files
Git workflows
git
Source: ./plugins/git
{ "name": "git", "source": "./plugins/git", "description": "Git workflows" }
Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.272k94k
Resolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.183k193kGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.175k193k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.149k263k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.6k37.2k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.16.5k148How it compares
Workflow-oriented git skill—not a hosted GitHub App or full git MCP with rich diff UI.
FAQ
Who is git for?
Developers who delegate routine git steps to their coding agent inside the claude-nine plugin ecosystem.
When should I use git?
During Build for branches and commits; during Ship when preparing or updating changes for review and merge.
Is git safe to install?
Git skills can suggest destructive commands; review the Security Audits panel on this Prism page and confirm commands before force-pushing or resetting.