Initialise a git repository with optional configuration for agent workflows.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionhere-be-gitExecute the skills CLI command in your project's root directory to begin installation:
Fetches here-be-git from intellectronica/agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate here-be-git. Access via /here-be-git in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
236
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
236
stars
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.**
- "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.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Keeps context tight: here-be-git is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for here-be-git matched our evaluation — installs cleanly and behaves as described in the markdown.
here-be-git is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: here-be-git is focused, and the summary matches what you get after install.
Useful defaults in here-be-git — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added here-be-git from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in here-be-git — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
here-be-git is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for here-be-git matched our evaluation — installs cleanly and behaves as described in the markdown.
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