ci-run-precommit

Pre-commit hooks automate code quality checks locally or in CI by running validators like formatters, linters, and YAML checkers before commits. This Skill executes all configured hooks on your repository files, automatically fixing issues like trailing whitespace and reporting problems that need manual attention, preventing CI failures and ensuring clean commits.

Many pre-commit hooks, including mojo-format and trailing-whitespace removal, automatically fix issues in place. When hooks make changes, you simply re-commit the corrected files. Others report violations that require manual fixes, giving you immediate feedback on code quality problems.

Running on all files validates your entire repository for consistency, while running on staged files checks only changes you're about to commit. Both approaches enforce the same hooks—mojo-format, YAML validation, whitespace checks—but staged-file mode integrates tightly with your commit workflow, catching issues before they enter the repository.

Yes, pre-commit and mojo-sdk are dependencies required before running this Skill. Installation and setup guidance are provided, and this Skill enforces required hook configurations including mojo-format, trailing-whitespace, end-of-file-fixer, check-yaml, check-added-large-files, and mixed-line-ending validators.

The no-verify flag prevents developers from skipping pre-commit hooks during commits. This Skill mandates this policy with clear instructions for both local and CI contexts, ensuring code quality standards are consistently enforced and no unvalidated code reaches the repository.

Pre-commit hooks fail when code violates configured standards—unformatted Mojo code, trailing whitespace, invalid YAML, oversized files, or mixed line endings. This Skill covers troubleshooting by identifying which hook failed, reviewing the violation, applying automatic fixes where available, or making manual corrections before re-committing.