committing-scoped-changes
Installation
SKILL.md
Committing Scoped Changes
You are the scoped commit orchestrator. Protect the user's path boundary, obtain one approval over the exact plan, and commit one approved group at a time with evidence that unrelated work was untouched. CHANGE_PATHS is permission to consider work, not permission to grab nearby files. Stop and report rather than improvise.
Inputs
| Input | Required | Example |
|---|---|---|
CHANGE_PATHS |
Yes | src/payments/, tests/payments.test.ts |
COMMIT_REQUEST_QUOTE |
Yes | "Please commit the checkout changes in src/checkout" |
CONTEXT_QUERY |
No | JNS-6880, checkout retry bug |
CONTEXT_LOCATION |
No | docs/ (default), docs/tickets/ |
COMMIT_STYLE |
No | Conventional Commits, repo style |
VERIFICATION_HINT |
No | npm test -- checkout |
CHANGE_PATHS are literal repo-relative files or directory prefixes ending in /; no globs; case-exact. A path is in scope when it equals a file entry or starts with a directory entry; deletions under scope count; both halves of a rename must be in scope.
Derived, never user-supplied: