devenv-pre-commit

To run linting and tests on modified files before a git commit, this skill scopes analysis to changed files since the merge-base. It automatically resolves and executes quality gate commands from project-specific configuration files or devenv conventions.

Automating code quality checks before committing involves running linting, formatting, type-checking, and testing workflows against your project. This skill automates these workflows and aggregates failures into a single actionable report with file-line references.

Yes, you can automatically fix formatting and linting issues during pre-commit verification. The skill suggests and applies tool-specific auto-fixes with explicit user confirmation before applying changes to your modified files.

Pre-commit quality gate automation works in multi-repo workspaces by scoping analysis to changed files since the merge-base. This ensures efficient verification across multiple repositories without running unnecessary checks.

Yes, you need project-specific configuration files or standard devenv conventions to run automated pre-commit checks. The skill requires these to intelligently detect project types and resolve the correct quality gate commands.

Your pre-commit skill may not resolve quality gate commands if it cannot find project-specific configuration files or standard devenv conventions. It relies on these inputs to intelligently detect project types and execute the correct linting and testing workflows.