Can I bypass these hooks in an emergency?

While git allows bypassing hooks using the --no-verify flag, this skill recommends doing so only for critical production hotfixes or when CI/CD systems are blocking urgent deploys.

How does this skill help with repository security?

It includes universal 'No Secrets' checks using tools like Gitleaks, which scan staged files for API keys, passwords, and other credentials before they can be committed.

Which programming languages are supported by this safety skill?

This skill provides specific implementation patterns and configurations for JavaScript/TypeScript (Husky), Python (pre-commit framework), and PHP/Laravel environments.

Why are pre-commit hooks considered mandatory by this skill?

Pre-commit hooks act as automated quality gates. Humans can forget to run tests or format code, but automated machines do not, ensuring that only high-quality, compliant code enters the repository.

Automated Pre-Commit Hooks

Name: Automated Pre-Commit Hooks
Author: liauw-media

byliauw-media

Security & Testing

Enforces mandatory code quality gates and security checks by automating linting, formatting, and testing before every git commit.

About

The Automated Pre-Commit Hooks skill implements 'The Iron Law' of professional development: no project should exist without automated quality enforcement. It provides domain-specific configurations for JavaScript, Python, and PHP environments to ensure that unformatted code, type errors, and broken tests never reach your repository. By standardizing the use of tools like Husky, pre-commit, and Gitleaks, this skill helps teams maintain a clean codebase, prevent credential leaks, and streamline the onboarding process for new developers.

Key Features

Multi-language support for JS/TS, Python, and PHP projects
Standardized linting and formatting enforcement (Prettier, Black, etc.)
Tailored test execution patterns for frontend and backend changes
Automated secret leak detection using Gitleaks integration
Conventional commit message validation for clean git histories
0 GitHub stars

Use Cases

Standardizing quality gates during the initialization of new software projects
Preventing sensitive credentials and API keys from being committed to version control
Automating code style and type checking to reduce friction during code reviews

About

Key Features

Multi-language support for JS/TS, Python, and PHP projects
Standardized linting and formatting enforcement (Prettier, Black, etc.)
Tailored test execution patterns for frontend and backend changes
Automated secret leak detection using Gitleaks integration
Conventional commit message validation for clean git histories
0 GitHub stars

Use Cases

Standardizing quality gates during the initialization of new software projects
Preventing sensitive credentials and API keys from being committed to version control
Automating code style and type checking to reduce friction during code reviews