Enforces Conventional Commits format for git commit messages. Use when formatting commits or validating message structures. For git commands, see git-control.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
| Type | When to Use |
|---|---|
feat | New feature or capability |
fix | Bug fix |
docs | Documentation only changes |
style | Formatting, missing semicolons, etc. (no code change) |
refactor | Code change that neither fixes a bug nor adds a feature |
perf | Performance improvement |
test | Adding or correcting tests |
build | Build system or external dependency changes |
ci | CI configuration changes |
chore | Other changes that don't modify src or test files |
Use the BRAINIAC phase or module name:
feat(idea): add competitor analysis playbookdocs(planning): update tech stack playbookfeat(skills): add market-research skillfix(landing-page): correct CTA linkAdd ! after type/scope for breaking changes:
feat(api)!: change authentication flow to OAuth2
Or use footer:
feat(api): change authentication flow
BREAKING CHANGE: JWT tokens are no longer accepted.
feat(idea): add structured competitor analysis playbook
docs(skills): create market-research skill with Firecrawl integration
fix(landing-page): correct hero section gradient on mobile
chore(tasks): reset todo.md for foundations sprint
refactor(playbooks): rewrite idea phase to match new template
Refs: #123<type>[scope]: <description> formatNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Generates and maintains changelogs following Keep a Changelog format. Use when updating release notes, finishing tasks, or tagging versions. For version bumps, see semantic-versioning.
The English summary is being prepared. Showing the original description.
Structured competitor teardown skill. Use when scraping competitor sites, extracting pricing/features/positioning, or analyzing strategic gaps. For general research, see market-research.
The English summary is being prepared. Showing the original description.
Creates an llms.txt file from scratch based on repository structure. Use when configuring LLM discovery files. For updating existing configurations, see update-llms.
The English summary is being prepared. Showing the original description.
Intelligent README.md generation prompt that analyzes project documentation structure and creates comprehensive repository documentation. Scans ./ directory files and creates a README.md file for the project. Only used when creating a new repository. or when the README.md file is missing.
The English summary is being prepared. Showing the original description.
Standardizes git operations, branch management, and disaster recovery. Use when committing, branching, or resolving conflicts. For commit formatting, see conventional-commits.
The English summary is being prepared. Showing the original description.
Structured validation framework that scores product ideas. Use when evaluating problem severity, willingness-to-pay, or founder-market fit. For market intelligence, see market-research.
The English summary is being prepared. Showing the original description.