precommit
Validate code changes before committing by analyzing security, performance, quality, tests, or breaking changes. Specify files, focus areas, and severity levels to ensure pre-commit checks meet project standards.
Instructions
Pre-commit validation for code changes
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| compareTo | No | Git ref to compare against (e.g., 'main', 'HEAD~1'). If not provided, analyzes current changes | |
| files | No | Specific files to validate (optional - will analyze git changes if not provided) | |
| focus | No | Validation focus area | all |
| includeStaged | No | Include staged changes in validation | |
| includeUnstaged | No | Include unstaged changes in validation | |
| provider | No | AI provider to use | gemini |
| severity | No | Minimum severity level to report | medium |
| task | Yes | What to validate for pre-commit (e.g., 'review changes before commit', 'validate security implications', 'check for breaking changes') |