← ClaudeAtlas

commitlisted

Commit staged changes with emoji+type conventions and formatting.
bravros/bravros · ★ 2 · Code & Development · score 76
Install: claude install-skill bravros/bravros
# commit INTENT: commit the current changes. Commit only — never push. HARD CONSTRAINTS: - Always `bravros commit "<emoji> <type>[(scope)]: <subject>" <files...>` — never raw `git add && git commit`. The verb runs the project formatter (pint / prettier / ruff / gofmt / cargo fmt) before committing, and the commit-msg hook enforces the format. - Name files explicitly — never blanket-stage. Never stage `.env`, `.env.*`, credentials, or API keys. - NEVER add AI signatures (`Co-Authored-By: Claude`, "Generated with…") — the hook rejects them. - Subject ≤ 50 chars (hard 72), present tense, lowercase, why over what; detail goes in the body. REPO FACT — the only accepted `<emoji> <type>` pairs: ✨ feat · 🐛 fix · 📚 docs · 💄 style · ♻️ refactor · ⚡ perf · 🧪 test · 🔧 build · 🧹 chore · 📋 plan · 🔒 security · 🗃️ migration · 📦 deps · 🚀 deploy · 🤖 ci · 🔥 remove · 🩹 hotfix · 🔀 merge · 🔍 debug · 🔙 revert · 🌐 i18n Use $ARGUMENTS as context for the commit message if provided.