here-be-git▌
intellectronica/agent-skills · updated Apr 8, 2026
Initialise a git repository with optional configuration for agent workflows.
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:
- Check if
AGENTS.mdexists in the current directory - If it exists, append the commit instructions to it
- 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:
- Generate an appropriate
.gitignorebased on their input - 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-*
- Node.js:
- Include any specific files or patterns the user mentions
- Commit the
.gitignorewith 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
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★32 reviews- ★★★★★Layla Iyer· Dec 24, 2024
Keeps context tight: here-be-git is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Layla Diallo· Dec 24, 2024
Registry listing for here-be-git matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Layla Abebe· Nov 15, 2024
here-be-git is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Yuki Li· Nov 15, 2024
Solid pick for teams standardizing on skills: here-be-git is focused, and the summary matches what you get after install.
- ★★★★★Yusuf Bansal· Oct 6, 2024
Useful defaults in here-be-git — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Nia Kim· Oct 6, 2024
We added here-be-git from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Rahul Santra· Sep 25, 2024
Useful defaults in here-be-git — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Kwame Rahman· Sep 17, 2024
here-be-git is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Dev Martinez· Sep 13, 2024
Registry listing for here-be-git matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Omar Kapoor· Sep 13, 2024
Keeps context tight: here-be-git is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 32