Your job is to create well-formatted commits with conventional commit messages and emoji.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongit:commitExecute the skills CLI command in your project's root directory to begin installation:
Fetches git:commit from neolabhq/context-engineering-kit 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:commit. Access via /git:commit 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
765
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
765
stars
Your job is to create well-formatted commits with conventional commit messages and emoji.
CRITICAL: Perform the following steps exactly as described:
master or main. If so, asks the user whether to create a separate branch before committing. If user confirms a new branch is needed, creates one using the pattern <type>/<username>/<description> (e.g., feature/leovs09/add-new-command)--no-verify, automatically runs pre-commit checks like pnpm lint or simular depending on the project language.git statusgit addgit diff to understand what changes are being committed<type>: <description> where type is one of:
feat: A new featurefix: A bug fixdocs: Documentation changesstyle: Code style changes (formatting, etc)refactor: Code changes that neither fix bugs nor add featuresperf: Performance improvementstest: Adding or fixing testschore: Changes to the build process, tools, etc.feat: New featurefix: Bug fixdocs: Documentationstyle: Formatting/stylerefactor: Code refactoringperf: Performance improvementstest: Testschore: Tooling, configurationci: CI/CD improvementsrevert: Reverting changestest: Add a failing testfix: Fix compiler/linter warningsfix: Fix security issueschore: Add or update contributorsrefactor: Move or rename resourcesrefactor: Make architectural changeschore: Merge brancheschore: Add or update compiled files or packageschore: Add a dependencychore: Remove a dependencychore: Add or update seed fileschore: Improve developer experiencefeat: Add or update code related to multithreading or concurrencyfeat: Improve SEOfeat: Add or update typesfeat: Add or update text and literalsfeat: Internationalization and localizationfeat: Add or update business logicfeat: Work on responsive designfeat: Improve user experience / usabilityfix: Simple fix for a non-critical issuefix: Catch errorsfix: Update code due to external API changesfix: Remove code or filesstyle: Improve structure/format of the codefix: Critical hotfixchore: Begin a projectchore: Release/Version tagswip: Work in progressfix: Fix CI buildchore: Pin dependencies to specific versionsci: Add or update CI build systemfeat: Add or update analytics or tracking codefix: Fix typosrevert: Revert changeschore: Add or update licensefeat: Introduce breaking changesassets: Add or update assetsfeat: Improve accessibilitydocs: Add or update comments in source codedb: Perform database related changesfeat: Add or update logsfix: Remove logstest: Mock thingsfeat: Add or update an easter eggchore: Add or update .gitignore filetest: Add or update snapshotsexperiment: Perform experimentsfeat: Add, update, or remove feature flagsui: Add or update animations and transitionsrefactor: Remove dead codefeat: Add or update code related to validationfeat: Improve offline supportWhen analyzing the diff, consider splitting commits based on these criteria:
Good commit messages:
Example of splitting commits:
--no-verify: Skip running the pre-commit checks (lint, build, generate:docs)When committing on master or main, the command will ask if you want to create a new branch. If yes, it creates a branch following this pattern:
<type>/<git-username>/<description>
Components:
<type>: The commit type (feature, fix, docs, refactor, perf, test, chore, etc.)<git-username>: Your git username (obtained from git config user.name or the system username)<description>: A kebab-case description of the change (e.g., add-user-auth, fix-login-bug)Examples:
feature/leovs09/add-new-commandfix/johndoe/resolve-memory-leakdocs/alice/update-api-docsrefactor/bob/simplify-error-handlingchore/charlie/update-dependenciesWorkflow:
master or mainpnpm lint, pnpm build, pnpm generate:docs) will run to ensure code qualityMake 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
pproenca/dot-skills
ailabs-393/ai-labs-claude-skills
mattpocock/skills
git:commit fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added git:commit from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in git:commit — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: git:commit is focused, and the summary matches what you get after install.
Registry listing for git:commit matched our evaluation — installs cleanly and behaves as described in the markdown.
git:commit has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: git:commit is focused, and the summary matches what you get after install.
git:commit is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added git:commit from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: git:commit is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 50