Creates scoped git commits with conventional message formatting and authorization checks.
npx skills add https://github.com/kwanpham2195/agent-stuff --skill commit-kwanpham2195
Please help me install this Agent Skill. Skill: commit Source: https://github.com/kwanpham2195/agent-stuff/tree/main/skills/commit Command: npx skills add https://github.com/kwanpham2195/agent-stuff --skill commit-kwanpham2195
git status and diffs, and stops to ask when unrelated changes create ambiguity. - Message Conventions: Follows the repository's documented convention or infers one from recent history, falling back to <type>(<scope>): <summary> format with types like feat, fix, docs, and refactor. - Safe Staging and Committing: Stages only explicit intended paths, reviews the cached diff before committing, keeps hooks enabled, and reports the resulting commit SHA. - Use Case: After finishing a bug fix, ask the agent to commit only the parser changes; it stages those files, writes fix(parser): reject empty input, runs hooks, and reports the SHA without touching unrelated work. ## Quick Start Commit only the changes in the src/parser directory with an appropriate conventional commit message.High-intent search queries and answers about installing and using this skill.
Use the format `<type>(<scope>): <summary>` with types like feat, fix, docs, refactor, chore, test, or perf. Keep the summary imperative, under 72 characters, with no trailing period, for example `fix(parser): reject empty input`.
Stage explicit intended paths with `git add <path>` rather than `git add -A`, then review `git diff --cached` before committing. If pre-staged changes fall outside your intended scope, stop and clarify rather than including or unstaging them.
First check for documented conventions, then inspect recent history with `git log -10 --pretty=format:%s` to infer the pattern. If neither establishes a convention, default to the conventional commits format with a type prefix and imperative summary.
No, committing does not authorize pushing, amending, or switching branches. Each of those actions requires separate explicit authorization from the user before proceeding.
Commits run with hooks enabled, and failures are fixed only within the authorized scope of the change. If a hook failure cannot be resolved within that scope, the blocker is reported rather than bypassed.
kreekStage reviewed changes by name and write structured git commit messages.
eriknovakCreate a conventional commit, push the branch, and open a GitHub pull request.
babuallyReview code changes against repository standards and originating specifications.
sasamukuCreate fixup commits and run autosquash rebase on a target branch.