Initialise a git repository with optional agent commit instructions and .gitignore. Use when users say "here be git", "init git", "initialise git", or otherwise indicate they want to set up version control in the current directory.
87
80%
Does it follow best practices?
Impact
100%
1.20xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/here-be-git/SKILL.mdInitialise a git repository with optional configuration for agent workflows.
Run git init in the current working directory. Confirm to the user that the repository has been initialised.
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:
AGENTS.md exists in the current directoryThe 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.
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:
.gitignore based on their inputnode_modules/, dist/, .env, *.log, etc.__pycache__/, *.pyc, .venv/, venv/, .env, *.egg-info/, etc..DS_Store, .AppleDouble, .LSOverride, ._*.idea/, .vscode/, *.swp, *.swo, *.sublime-*.gitignore with an appropriate messageIf the user declines, skip this step.
9f7f750
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.