tuliosousapro/saas-blueprint/conventional-commits

Conventional Commits Skill

When to Use

• Every time a git commit is made
• When the user asks to "commit this" or "save progress"
• When auto-committing after task completion

Reference

Conventional Commits v1.0.0

Instructions

1. Commit Message Format

<type>[optional scope]: <description>
 
[optional body]
 
[optional footer(s)]

2. Types

3. Scope (Optional)

Use the BRAINIAC phase or module name:

• feat(idea): add competitor analysis playbook
• docs(planning): update tech stack playbook
• feat(skills): add market-research skill
• fix(landing-page): correct CTA link

4. Breaking Changes

Add ! 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.

5. Examples

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

6. Rules

• Description: lowercase, imperative mood, no period at end
• Max 72 characters for the first line
• Body wraps at 100 characters
• One logical change per commit
• Reference issue numbers in footer when applicable: Refs: #123

Quality Gates

• First line matches <type>[scope]: <description> format
• Type is from the approved list
• Description is imperative mood ("add" not "added", "fix" not "fixed")
• No commits with generic messages like "update", "fix stuff", "wip"