pre-commit-review

Enforce pre-commit quality gates with static analysis, unit tests, and security scans.

1|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/constellize/marketplace --skill pre-commit-review-constellize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-commit-review
Source: https://github.com/constellize/marketplace/tree/main/plugins/constellize-ai-workflow/skills/pre-commit-review
Command: npx skills add https://github.com/constellize/marketplace --skill pre-commit-review-constellize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforce pre-commit quality gates to prevent issues from entering the shared repository, ensuring only clean, secure, and well-tested changes are accepted.

Core Features & Use Cases

  • Static analysis and linting to catch code style violations, potential bugs, and maintainability concerns in changed files.
  • Unit-test gates to require tests pass and meet minimum coverage thresholds for new or modified code.
  • Security scans to detect hardcoded secrets and known dependency vulnerabilities before integration.
  • Dependency safety checks to assess licenses, maintenance status, and security posture of updated dependencies.
  • Use cases include enforcing a clean baseline in CI, guiding contributors before submission, and reducing risk across services.

Quick Start

Configure the pre-commit gates in your repository and run a small commit to see the checks execute.

Frequently Asked Questions about pre-commit-review

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

FAQPage Schema
How do I enforce pre-commit quality gates for static analysis and security scans?

Pre-commit quality gates enforce static analysis and security scans by applying checks directly to changed files, preventing code style violations and hardcoded secrets from entering the shared repository.

What is the best way to run unit tests and dependency checks before committing code changes?

The best way to run unit tests and dependency checks pre-commit is to configure gates that validate modified files against coverage thresholds and assess dependency licenses and security posture.

Does pre-commit static analysis provide fast per-file feedback for large repositories?

Pre-commit static analysis provides fast, per-file feedback by targeting only changed files rather than the entire codebase, ensuring quick local validation before integration into shared services.

Can I bypass pre-commit security scans and unit-test gates during an emergency deployment?

Pre-commit security scans and unit-test gates can be bypassed during emergencies, but the Skill requires generating a documented bypass trail to maintain accountability and reduce integration risk.

Why do I need dependency safety checks in my pre-commit hooks?

Dependency safety checks are needed in pre-commit hooks to assess updated dependencies for vulnerable licenses, poor maintenance status, and known security vulnerabilities before they are integrated into the codebase.