Here Be Git
- 484 installs
- 281 repo stars
- Updated April 25, 2026
- intellectronica/agent-skills
here-be-git is an agent skill that initializes a git repository with optional AGENTS.md commit instructions and .gitignore templates for developers who want safe agent-driven version control from day one.
About
here-be-git is a Git & Pull Requests agent skill from intellectronica/agent-skills that runs a three-step workflow when a developer says "here be git", "init git", or wants version control in the current directory. Step 1 runs git init and confirms the repository. Step 2 optionally appends mandatory agent commit instructions to AGENTS.md—or creates that file—requiring commits after every task with no exceptions. Step 3 optionally generates a .gitignore from flavours like Node.js, Python, macOS, or IDE patterns, then commits each change atomically. If git is already initialized, the skill skips init and proceeds to agent instructions. here-be-git helps teams prevent agents from leaving uncommitted changes and establish repository hygiene before feature work begins.
- Git history and branch exploration
- Safer commit and PR preparation
- Reduces destructive git mistakes
- Repo navigation for agent workflows
- Supports multi-surface codebases
Here Be Git by the numbers
- 484 all-time installs (skills.sh)
- +11 installs in the week ending Aug 2, 2026 (Skillselion tracking)
- Ranked #108 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/intellectronica/agent-skills --skill here-be-gitAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 484 |
|---|---|
| repo stars | ★ 281 |
| Last updated | April 25, 2026 |
| Repository | intellectronica/agent-skills ↗ |
How do you initialize git with agent commit rules?
Navigate git history, branches, and PR hygiene safely so agents inspect repos, prepare commits, and avoid destructive version-control mistakes.
Who is it for?
Developers starting a new project who want git initialized plus enforced agent commit discipline and a tailored .gitignore in one workflow.
Skip if: Repositories already configured with git remotes, branching strategy, and established commit conventions that should not be overwritten.
When should I use this skill?
User says "here be git", "init git", "initialise git", or asks to set up version control with agent commit instructions.
What you get
Initialized git repository, optional AGENTS.md with mandatory commit workflow, and optional committed .gitignore file.
- git repository
- AGENTS.md commit instructions
- .gitignore file
By the numbers
- Three-step workflow: git init, AGENTS.md commit rules, optional .gitignore
Files
Here Be Git
Initialise a git repository with optional configuration for agent workflows.
Workflow
Step 1: Initialise Git Repository
Run git init in the current working directory. Confirm to the user that the repository has been initialised.
Step 2: Agent Commit Instructions
Ask the user:
Would you like me to add instructions for the agent to always commit when it's done with a task?
If the user confirms:
1. Check if AGENTS.md exists in the current directory 2. If it exists, append the commit instructions to it 3. If it doesn't exist, create it with the commit instructions
The commit instructions to add:
## Git Workflow — CRITICAL, MANDATORY, NO EXCEPTIONS
> **THIS IS NOT OPTIONAL.** Every agent operating in this repository MUST follow this workflow after every change, no matter how small. There are ZERO exceptions to this rule. Skipping a commit is never acceptable. If you have made any change to any file, you MUST commit before moving on.
### Rules
1. **ALWAYS commit your changes immediately after completing a task or reaching any logical stopping point.** Do not defer. Do not batch. Do not skip.
2. **ALWAYS commit before ending your session.** The working directory MUST be clean (all changes committed) when you finish. Leaving uncommitted changes is a failure state.
3. **Use clear, descriptive commit messages** that explain what was done and why.
4. **If in doubt, commit.** It is always better to have one commit too many than one too few.
### To be absolutely clear
- "I'll commit later" — **No. Commit now.**
- "It's just a small change" — **Commit it.**
- "I'm about to make another change" — **Commit the current one first.**
- "The user didn't ask me to commit" — **Irrelevant. Commit anyway.**After creating or updating AGENTS.md, commit it with an appropriate message.
Step 3: Gitignore Configuration
Ask the user:
Would you like me to create a .gitignore? If so, what flavour or patterns should I include? (e.g., Node.js, Python, macOS, IDE files, or specific files/patterns)
If the user provides a flavour or patterns:
1. Generate an appropriate .gitignore based on their input 2. For common flavours, include standard patterns:
- Node.js:
node_modules/,dist/,.env,*.log, etc. - Python:
__pycache__/,*.pyc,.venv/,venv/,.env,*.egg-info/, etc. - macOS:
.DS_Store,.AppleDouble,.LSOverride,._* - IDE files:
.idea/,.vscode/,*.swp,*.swo,*.sublime-*
3. Include any specific files or patterns the user mentions 4. Commit the .gitignore with an appropriate message
If the user declines, skip this step.
Notes
- If git is already initialised in the directory, inform the user and skip to Step 2
- Use the AskUserQuestion tool for the confirmation prompts
- Keep commits atomic and well-described
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
Use here-be-git over manual git init when agents must follow enforced commit discipline via AGENTS.md from the first commit.
FAQ
What does here-be-git do when git is already initialized?
here-be-git informs the developer that git already exists, skips git init, and proceeds to Step 2 where it can add optional AGENTS.md commit instructions and a .gitignore if the user requests them.
What commit rules does here-be-git add to AGENTS.md?
here-be-git adds mandatory rules requiring agents to commit immediately after every task, commit before ending a session, use descriptive messages, and never leave uncommitted changes regardless of task size or user request.