create-pr-commit
Create Commit / PR / Branch Names
Overview
Produce high-signal Git metadata that matches the repository's actual conventions instead of inventing random types or scopes.
Workflow
- Classify the change intent
- Determine the primary change type:
feat,fix,docs,style,refactor,perf,test,build,ci,chore, orrevert. - If multiple apply, choose the dominant user-facing impact.
- Determine the primary change type:
More from hugorcd/skills
unslop
Remove AI-generated "slop" from codebases by deleting redundant comments and unused code, tightening formatting, and normalizing styling patterns (e.g., Tailwind class consistency, Nuxt UI color tokens). Use when a user asks to clean up code, remove unnecessary comments, reduce unused imports/variables, or align Tailwind/Nuxt UI conventions.
8setup-for-oss
Review and bootstrap open-source repo health (OSS) by auditing or scaffolding README, CONTRIBUTING, CODE_OF_CONDUCT, LICENSE, SECURITY, GitHub templates, CI workflows, Renovate, publishing (pkg-pr-new + npm Trusted Publishing), linting/formatting, Changesets, and automation. Use when asked to review OSS setup, check OSS health, or set up/add OSS files and workflows.
5