auto-commit

Group files that must change together, such as an implementation file with its matching test, and stage each logical group separately. This Skill automates that process by analyzing git status, applying atomic grouping heuristics, and creating one conventional commit per logical change.

Block sensitive paths such as .env, *.key, *.pem, and credentials files before staging, then scan the staged diff for tokens, passwords, and private key blocks. This Skill performs both checks and halts without committing if any secret indicator is found.

Conventional Commits use the format type(scope): description, with types like feat, fix, docs, and refactor. Subjects stay under 72 characters in imperative mood, and breaking changes are marked with an exclamation mark or a BREAKING CHANGE footer.

No, it executes immediately upon invocation without asking for approval of staging, messages, or commits. It only halts on git errors, failed secret scans, or ambiguous safety states, then reports the blocking reason.

The Skill unstages the flagged files with git restore --staged, halts execution, and reports only the file paths and matched rule names. It never prints secret values, requests overrides, or commits flagged files.