commit-safe

The commit-safe skill acts as an intelligent Git workflow assistant designed to improve code quality and transparency by enforcing disciplined staging practices. It is intended for software engineers and technical researchers who work within Git-managed repositories and wish to avoid the common pitfalls of 'git add -A' or 'git add .', which often lead to bloated commits or the accidental inclusion of sensitive files. By monitoring the state of the working directory, the agent offers proactive guidance on staging files, structuring commits, and following conventional commit message formats.

• Actively intercepts potential mass-staging actions and suggests reviewing changes via git status and git diff --stat before finalizing.

• Enforces a clear, semantic commit message convention (e.g., feat, fix, docs, refactor, test) to ensure a clean and searchable Git history.

• Provides a safety-wrapper interface via a custom shell script (scripts/commit.sh) to ensure all commits are signed and correctly labeled.

• Encourages the logical grouping of related changes, promoting granular, atomic commits that make code reviews more efficient.

• Offers real-time suggestions when detecting multi-file modifications or high-risk repository states.

• Recommended for use in research templates or professional coding environments where history cleanliness is a priority.

• Strictly prohibits the commit of sensitive files like .env or local credential stores through pre-commit verification prompts.

• Requires developers to explicitly stage specific files, effectively decoupling complex changes into smaller, manageable chunks.

• Operates by monitoring changes in the working tree and interacting with the user to confirm intent before staging operations occur.

• Operates best when integrated with projects that utilize specific commit-handling scripts to prevent AI-signature leakage and maintain standardized documentation standards.