Commits staged changes with enforced emoji and type conventions after running project formatters.
npx skills add https://github.com/bravros/bravros --skill commit-bravros
Please help me install this Agent Skill. Skill: commit Source: https://github.com/bravros/bravros/tree/main/plugins/core/skills/commit Command: npx skills add https://github.com/bravros/bravros --skill commit-bravros
bravros commit with a fixed set of emoji+type pairs (✨ feat, 🐛 fix, ♻️ refactor, and 18 more) validated by a commit-msg hook. - Automatic formatting: Runs the project formatter (pint, prettier, ruff, gofmt, or cargo fmt) before committing. - Safety guardrails: Requires explicit file naming, blocks staging of .env files and credentials, and rejects AI signatures like Co-Authored-By: Claude. - Use Case: After fixing a login bug, ask the agent to commit only auth/login.go and auth/login_test.go; it formats the code, then creates a commit like 🐛 fix(auth): reject expired refresh tokens without pushing. ## Quick Start Ask the agent to commit the current changes for the files you name, for example: commit the staged fix in src/auth.go using the commit skill.High-intent search queries and answers about installing and using this skill.
Use the format `<emoji> <type>[(scope)]: <subject>`, for example `🐛 fix(auth): reject expired tokens`. Keep the subject under 50 characters, in present tense and lowercase, and put extra detail in the commit body.
Run `bravros commit "<emoji> <type>: <subject>" <files...>` with the specific files to include. The command formats and commits only; pushing is handled separately by the push or ship workflows.
The accepted pairs include ✨ feat, 🐛 fix, 📚 docs, 💄 style, ♻️ refactor, ⚡ perf, 🧪 test, 🔧 build, 🧹 chore, 🔒 security, 🗃️ migration, 📦 deps, 🚀 deploy, 🤖 ci, 🔥 remove, 🩹 hotfix, 🔀 merge, 🔍 debug, 🔙 revert, and 🌐 i18n.
Rejections happen when the message lacks a valid emoji+type pair, the subject exceeds the length limit, or it contains AI signatures like `Co-Authored-By: Claude`. Remove the signature and match one of the 21 accepted pairs.
It depends on the repository policy. Run `bravros config get police.direct_main`; if it prints `true`, committing on main is normal, otherwise the repo is PR-gated and you should create a branch first.
Blanket staging can sweep in `.env` files, credentials, or API keys, which must never be committed. Name each file explicitly in the commit command so only intended changes are staged.
davila7Creates logically scoped git commits with Conventional Commits messages using selective staging.
TumeloRamaphosaMerge base branch, run tests, bump VERSION, update CHANGELOG, commit, push, and open a PR.
LordjiggyConfigure git hooks for pre-commit linting, formatting, tests, and commit-msg conventions.
openclawDetect duplicate GitHub PRs and issues, group them in prtags, and sync annotations.