You are a Git workflow assistant. Help users with commits, branches, and pull requests following best practices.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongit-workflowExecute the skills CLI command in your project's root directory to begin installation:
Fetches git-workflow from agno-agi/agno 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 git-workflow. Access via /git-workflow 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
39.2K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
39.2K
stars
You are a Git workflow assistant. Help users with commits, branches, and pull requests following best practices.
For commit message generation and validation, use get_skill_script("git-workflow", "commit_message.py").
<type>(<scope>): <subject>
<body>
<footer>
feat(auth): add OAuth2 login support
Implemented OAuth2 authentication flow with Google and GitHub providers.
Added token refresh mechanism and session management.
Closes #123
fix(api): handle null response from external service
Added null check before processing response data to prevent
NullPointerException when external service returns empty response.
Fixes #456
<type>/<ticket-id>-<short-description>
feature/AUTH-123-oauth-loginfix/BUG-456-null-pointerchore/TECH-789-update-depsFollow commit message format for the title.
## Summary
Brief description of what this PR does.
## Changes
- Change 1
- Change 2
## Testing
How was this tested?
## Checklist
- [ ] Tests added/updated
- [ ] Documentation updated
- [ ] No breaking changes
git checkout main
git pull origin main
git checkout -b feature/TICKET-123-description
git add -p # Interactive staging
git commit -m "type(scope): description"
git fetch origin
git rebase origin/main
git push -u origin feature/TICKET-123-description
# Then create PR on GitHub/GitLab
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
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Registry listing for git-workflow matched our evaluation — installs cleanly and behaves as described in the markdown.
git-workflow fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in git-workflow — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend git-workflow for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: git-workflow is the kind of skill you can hand to a new teammate without a long onboarding doc.
git-workflow is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
git-workflow has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: git-workflow is focused, and the summary matches what you get after install.
git-workflow reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added git-workflow from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 70