commit-prep-helper

Pre-commit checks automate quality gates—linting, testing, and code review—on staged files before committing. This Skill detects your project type (Node.js, Python, Rust, Go), runs language-specific tools like ESLint or pytest, and generates a Conventional Commits message, ensuring every commit meets quality standards without manual steps.

Yes. This Skill automatically detects your project type and applies appropriate tools: ESLint and Jest for Node.js/TypeScript, Black and pytest for Python, cargo for Rust, and gofmt for Go. It adapts to your language, so you don't configure tooling per project.

Conventional Commits is a specification for commit messages that include type (fix, feat, etc.), scope, and description. It standardizes commit history, automates changelog generation, and clarifies intent. This Skill generates compliant messages automatically from your changes and quality checks.

Yes. This Skill performs staged file detection, runs project-specific linting and tests with coverage, executes static code review (checking security, quality, and complexity), then generates a commit message summarizing all findings—all in one workflow.

Quality checks (lint, tests, code review) run on staged changes. If issues are found, the Skill reports them before committing, letting you fix problems locally. The commit only proceeds when checks pass, preventing flawed commits from reaching your repository.