Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →mkurman/here-be-git
Initialise a git repository with optional agent commit instructions and .gitignore.
Passed 8 of 21 test cases with the skill, and 13 of 21 without it.
2 fixed12 passed either way6 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am in a folder where `.git` already exists. I want to execute the setup flow for agent configuration and ignore rules. Should git init be run again?
| Checked | Without skill | With skill |
|---|---|---|
| Informs the user that git is already initialized. | Passed | Passed |
| Skips git init and proceeds directly to asking about agent configuration. | Missed | Passed |
The instructions your model reads when the skill loads.
Initialise 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.**
test cases passed, vs 13 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.