Formats Conventional Commit messages and stages files atomically for git commits.
npx skills add https://github.com/camercu/dotfiles --skill commit-camercu
Please help me install this Agent Skill. Skill: commit Source: https://github.com/camercu/dotfiles/tree/main/common/.config/agents/skills/conventional-commits Command: npx skills add https://github.com/camercu/dotfiles --skill commit-camercu
<type>(<scope>): <description> messages with correct breaking-change notation (! plus BREAKING CHANGE: footer) and pre-1.0.0 MINOR-bump semantics. - Lint-safe body wrapping: Feeds git commit -F a process substitution piped through fmt -w 72 so body lines always stay under the commitlint 100-character limit without temp files or heredocs. - Atomic staging: Commits only explicitly listed paths, resetting the index for new files so parallel agent edits are never swept in. - Use Case: After editing two source files, ask for a commit and receive a properly scoped, wrapped, breaking-change-aware message applied to exactly those files. ## Quick Start Ask the assistant to commit your changed files with a conventional commit message, for example by saying commit this work.High-intent search queries and answers about installing and using this skill.
Use the format <type>(<scope>): <description>, such as feat(auth): add login endpoint. For a subject-only commit, run git commit -m with the message and explicit file paths; add a body only for non-obvious reasoning.
Mark breaking changes with an exclamation mark after the type or scope, plus a BREAKING CHANGE: footer in the body. Before version 1.0.0, breaking changes bump the MINOR version rather than MAJOR.
Commitlint rejects body lines over 100 characters, and manually guessing line breaks with multiple -m flags fails repeatedly. Pipe the body through fmt -w 72 inside a process substitution passed to git commit -F so every line stays under the limit.
Pass explicit paths after the message: git commit -m "msg" -- path/to/file1 path/to/file2. For brand-new files, first run git restore --staged :/ then git add the specific paths before committing.
fmt cannot break a single token longer than 100 characters, such as a long URL or file path, so that line may still trip commitlint. The workaround is to shorten the token or accept the lint flag in those rare cases.
ebknStage and commit changes with conventional messages and logical grouping.
MS33834Stages, commits, pushes, and opens a GitHub pull request for a linear change.
Coverage-CreativesAutomate code quality checks with Git hooks, lint-staged, Husky, and Commitlint.
roanbrasilImplement Git branching strategies, commit discipline, and PR practices.