here-be-git
Install this skill
npx skills add intellectronica/agent-skillsWorks across Claude Code, Cursor, Codex, Copilot & Antigravity
The here-be-git skill automates the setup of version control environments tailored for autonomous agent operations. Rather than simply running a git initialization command, this tool establishes a standardized communication protocol between the developer and the agent. It manages the creation of AGENTS.md to store persistent behavioral directives and links them into CLAUDE.md for visibility. The skill also facilitates the generation of context-aware .gitignore files, preventing common repository pollution from dependency folders or operating system metadata. By automating these baseline configurations, the tool ensures that every repository is ready for agentic participation, enforcing consistent commit habits and keeping the project structure clean from the moment initialization begins. It bridges the gap between a raw code directory and an agent-friendly, trackable development environment.
When to Use This Skill
- •Setting up a new project directory to support automated agent coding tasks
- •Standardizing repository instructions for agents across multiple local projects
- •Quickly creating a .gitignore for Node.js or Python environments during initialization
- •Enforcing consistent commit habits by documenting expectations in project metadata
How to Invoke This Skill
Example prompts that trigger this skill in Claude Code, Cursor, or Antigravity:
- “Initialize git and configure for agents
- “Start a new git repo and add agent commit instructions
- “Set up version control with my standard agent configuration
- “Create a repo and add a gitignore for python
- “Configure this directory for agent-assisted version control
Pro Tips
- 💡**Customize AGENTS.md**: After initialization, review and further customize the `AGENTS.md` file to include additional specific guidelines pertinent to your team or project's Git workflow, ensuring tailored agent behavior.
- 💡**Integrate .gitignore**: Although not explicitly part of this skill's core function, always follow up by having the agent generate a relevant `.gitignore` file to prevent unwanted files from being committed.
- 💡**Initial Commit**: Instruct the agent to perform an immediate initial commit after the setup is complete, perhaps with a message like 'Initial project setup with Git and agent configs.' to establish a clean starting point.
What this skill does
- •Executes git repository initialization in the current directory
- •Appends standardized commit behavioral instructions to AGENTS.md
- •Links AGENTS.md documentation within CLAUDE.md to ensure agent compliance
- •Generates language or platform-specific .gitignore templates
- •Performs initial commits for all auto-generated configuration files
When not to use it
- ✕Existing repositories where manual .gitignore and commit policies are already established
- ✕Environments where version control is not required or forbidden by project guidelines
Example workflow
- Trigger the tool in the target directory
- Confirm the repository initialization step
- Accept the agent commit instructions prompt to generate or update AGENTS.md
- Verify the automatic linking of AGENTS.md inside CLAUDE.md
- Select the appropriate .gitignore pattern based on the project stack
- Review the final automated commit summarizing the setup
Prerequisites
- –Git installed on the host system
- –Write permissions for the target directory
Pitfalls & limitations
- !Might overwrite existing content if AGENTS.md or CLAUDE.md are not formatted as expected
- !Requires manual intervention for complex .gitignore patterns not covered by standard templates
- !Assumes the agent has permission to modify existing version control files
FAQ
How it compares
Unlike a standard `git init`, this skill actively writes and links project documentation that governs agent behavior, ensuring the development environment is self-documenting for AI participants.
📄 Full skill instructions — original source: intellectronica/agent-skills
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 directory2. 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
- Always commit your changes when you have completed a task or reached a logical stopping point
- Use clear, descriptive commit messages that explain what was done and why
- Ensure the working directory is clean (all changes committed) before ending your sessionAfter creating or updating
AGENTS.md:1. Check if
CLAUDE.md exists in the current directory2. If it doesn't exist, create it with just
@AGENTS.md followed by a newline3. If it exists but doesn't already have
@AGENTS.md at the top, prepend @AGENTS.md followed by a newline to the existing content4. Commit both files together 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 input2. 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 messageIf 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
How to Use This Skill Unit
Option A: Project-Specific (Recommended)
- Click "Download" above
- In your project, create the directory:
.agent/skills/here-be-git/ - Save the file as
SKILL.md - The agent will automatically discover the skill based on its description.
Option B: Global Installation (All Agents)
Save the file to these locations to make it available across all projects:
- Claude Code:
~/.claude/skills/intellectronica/agent-skills/here-be-git/SKILL.md - Cursor:
~/.cursor/skills/intellectronica/agent-skills/here-be-git/SKILL.md - Antigravity:
~/.gemini/antigravity/skills/intellectronica/agent-skills/here-be-git/SKILL.md
🚀 Install with CLI:npx skills add intellectronica/agent-skills