Format commit messages according to Grey Haven Studio's actual commitlint configuration (100 char header, lowercase subject, conventional commits). Use when creating git commits or reviewing commit messages.
/plugin marketplace add greyhaven-ai/claude-code-config/plugin install linear@grey-haven-pluginsThis skill is limited to using the following tools:
checklists/commit-checklist.mdexamples/INDEX.mdexamples/frontend-examples.mdtemplates/simple-commit.txttemplates/with-body.txtFollow Grey Haven Studio's actual commit message standards, enforced by commitlint configuration from production templates.
<type>(<scope>): <subject>
[optional body]
[optional footer]
These rules are automatically enforced by commitlint:
Use exactly these types from Grey Haven's commitlint configuration:
| Type | Use Case | Example |
|---|---|---|
| feat | New feature for the user | feat(auth): add magic link authentication |
| fix | Bug fix for the user | fix(api): resolve race condition in order processing |
| docs | Documentation changes only | docs(readme): update TanStack Start setup guide |
| style | Code style changes (formatting) - no logic changes | style: apply Prettier to all TypeScript files |
| refactor | Code refactoring - neither fixes a bug nor adds a feature | refactor(repositories): simplify user query logic |
| test | Adding or updating tests | test(auth): add integration tests for OAuth flow |
| chore | Maintenance tasks, dependency updates | chore(deps): upgrade React to v19.1.0 |
| perf | Performance improvements | perf(db): add composite index on user_id and created_at |
| ci | CI/CD configuration changes | ci: add Vitest coverage threshold check |
| build | Build system or dependency changes | build: configure bun for monorepo |
| revert | Revert a previous commit | revert: feat(auth): add OAuth authentication |
Any other type will be REJECTED by commitlint.
feat(auth): add OAuth provider for Google authentication
^---------^ = 9 chars (type + scope)
^----------------------------------------^ = 45 chars (subject)
Total: 54 characters (within 100 limit ✅)
feat(auth): add password reset with email verification
fix(api): prevent duplicate user email registrations
docs: update API authentication guide with examples
refactor(utils): simplify date formatting helper functions
perf(db): add composite index on user_id and created_at
❌ feat(auth): Add OAuth provider # Uppercase 'A' (violates subject-case)
❌ Fix bug in API # Uppercase 'F' (violates subject-case)
❌ feat: add new feature. # Period at end
❌ WIP # Not a valid type
❌ added new endpoint # Missing type
❌ feat(api): Added endpoint and updated schema and added validation and wrote tests and updated docs
# Exceeds 100 characters
The scope should indicate which part of the codebase is affected:
auth, ui, forms, layout, routes, queries, db, serverapi, models, repositories, services, schemas, db, utils, configdeps, docker, deploy, scripts, ci, hooksScope is optional - omit if change affects multiple areas or is global.
Use the body to provide additional context when needed.
Start with BREAKING CHANGE: followed by description:
feat(api): migrate user IDs to UUID format
Change user ID format from sequential integers to UUIDs for better
scalability and security in multi-tenant architecture.
BREAKING CHANGE: User IDs are now UUIDs instead of sequential integers.
All API clients must update to handle UUID format. Database migration
required before deploying this change.
Fixes GREY-456
Related to GREY-123
Fixes #234
Closes #456
Related to #789
All supporting files are under 500 lines per Anthropic best practices:
examples/ - Complete commit message examples
reference/ - Configuration and rules
templates/ - Copy-paste ready templates
checklists/ - Pre-commit validation
Before committing, verify:
Use this skill when:
These standards come from Grey Haven's actual templates:
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.