run-precommit

Execute pre-commit hooks on staged or all repository files.

18|5|Updated Nov 3, 2025
One-click install
npx skills add https://github.com/HomericIntelligence/ProjectOdyssey --skill run-precommit-homericintelligence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-precommit
Source: https://github.com/HomericIntelligence/ProjectOdyssey/tree/main/.claude/skills/run-precommit
Command: npx skills add https://github.com/HomericIntelligence/ProjectOdyssey --skill run-precommit-homericintelligence

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates code quality checks using pre-commit hooks, preventing low-quality or malformed code from being committed and ensuring CI pipelines pass.

Core Features & Use Cases

  • Automated Code Validation: Runs pre-commit hooks to format code, check for trailing whitespace, ensure proper file endings, validate YAML, and prevent large files.
  • CI Pre-check: Helps ensure that code changes will pass automated checks in the CI environment.
  • Use Case: Before committing a new feature, run this skill to automatically format your Mojo code and catch any syntax errors or style issues, saving you from CI failures and review cycles.

Quick Start

Run the run-precommit skill to check all staged files for quality issues.

Frequently Asked Questions about run-precommit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run pre-commit hooks to check staged files for code quality?

To run pre-commit hooks on staged files, execute the validation skill to automatically check code formatting, trailing whitespace, file endings, YAML syntax, and large file additions. This prevents low-quality code from being committed and catches errors before CI pipelines run.

What code quality issues do pre-commit hooks catch before pushing to CI?

Pre-commit hooks catch code formatting issues, trailing whitespace, incorrect file endings, YAML syntax errors, and large file additions. Running these checks locally prevents CI failures by ensuring adherence to coding standards before code is committed.

Can I validate all files in a repository or only staged files with pre-commit?

You can validate both staged files and all files within a repository. The skill executes pre-commit hooks on the selected scope, checking for formatting, whitespace, YAML syntax, and large file additions to ensure code quality standards are met.

When do I need to run pre-commit hooks for automated code formatting?

You need to run pre-commit hooks before committing new features or code changes. This automates code formatting, catches syntax errors and style issues early, and saves you from CI failures and subsequent review cycles.

Why do my CI pipelines fail due to code formatting and whitespace issues?

CI pipelines fail when code contains formatting issues, trailing whitespace, or syntax errors that haven't been validated locally. Running pre-commit hooks before committing catches these issues early, ensuring code changes pass automated CI environment checks.