skills.rest
melodic-software
melodic-softwareOFFICIAL
Explore all skills by this author →
WebsiteGitHub

hooks-meta

Configure git hooks for code quality, security, and automated testing.

5|1|Updated Jun 22, 2026
Search Tags:#code quality#automation#validation#hooks#configuration#enforcement#PostToolUse#PreToolUse
One-click install
npx skills add https://github.com/melodic-software/claude-code-plugins --skill hooks-meta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hooks-meta
Source: https://github.com/melodic-software/claude-code-plugins/tree/main/plugins/claude-ecosystem/skills/hooks-meta
Command: npx skills add https://github.com/melodic-software/claude-code-plugins --skill hooks-meta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manually enforcing repository rules and best practices can be inconsistent and time-consuming. This skill centralizes the management and automation of Claude Code hooks to ensure consistent validation and auto-correction, freeing up developer time.

Core Features & Use Cases

  • Automated Rule Enforcement: Manages PreToolUse (validation) and PostToolUse (auto-fix) hooks to enforce critical repository rules like GPG signing, absolute path blocking, and markdown linting.
  • Vertical Slice Architecture: Organizes hooks with high cohesion, keeping all code, config, docs, and tests for each hook in a single, independent directory.
  • Flexible Configuration: Allows global and per-hook control over enablement, enforcement levels (block, warn, log), and custom patterns via YAML files with hot reload.
  • Comprehensive Development Guidance: Provides workflows for creating, testing, and debugging hooks, along with best practices for multi-language support and error handling.
  • Use Case: A team wants to ensure all Git commits are GPG signed and markdown files are automatically linted. This skill guides them through enabling and configuring the require-gpg-signing and markdown-lint hooks, automating these critical quality gates.

Quick Start

Use the hooks-meta skill to find out how to disable the require-gpg-signing hook temporarily.

Frequently Asked Questions about hooks-meta

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

FAQPage Schema
How do I enforce git hooks to validate code quality automatically?▼

Git hooks automate validation and fixes on commits by running pre-commit, commit-msg, and pre-push checks. This skill configures frameworks like Husky, lefthook, or Husky.Net to block invalid commits, scan secrets, lint markdown, enforce GPG signing, and standardize commits via conventional commit rules across .NET, JavaScript, Python, and polyglot projects.

Can I set up git hooks to automatically fix code instead of just blocking commits?▼

Yes. PostToolUse hooks auto-fix issues before commits complete—linting markdown, formatting code, or correcting common errors. This skill guides configuring both PreToolUse validation hooks and PostToolUse auto-fix hooks with enforcement levels (block, warn, log) to catch and resolve problems without manual intervention.

What's the best way to manage hooks consistently across a team?▼

Centralize hook configuration in YAML files with hot reload, enabling global and per-hook control. This skill provides standardized setup for multi-language teams, conventional commits, and frameworks like Husky, lefthook, or pre-commit, ensuring every developer enforces the same validation and testing rules without manual configuration drift.

Do git hooks work with .NET, JavaScript, Python, and multiple languages at once?▼

Yes. This skill covers setup for .NET/C#, JavaScript/TypeScript, Python, and polyglot repositories. It supports framework selection (Husky.Net for .NET, Husky for Node, lefthook for cross-language) with parallel execution where supported and copy-paste ready examples that scale from solo developers to large teams.

How do I temporarily disable a specific git hook like GPG signing validation?▼

Git hooks configured with flexible enforcement allow per-hook enablement control via YAML configuration. This skill guides disabling individual hooks—such as require-gpg-signing—temporarily or permanently while keeping other validations active, with hot reload support for immediate effect without repository changes.

Can git hooks integrate with CI/CD pipelines and secret scanning?▼

Yes. This skill covers CI/CD integration and secret scanning as part of hook configuration. Pre-push hooks can block commits containing secrets before they reach repositories, and hooks standardize local validation to match upstream CI rules, reducing failed pipeline runs and catching issues early.

Related Skills

Explore More Software Engineering Skills→
moughamirmoughamir

git-security-2025

Enforce signed commits and secret scanning across GitHub, GitLab, and Azure DevOps.

Community
Advanced
adaptive-enforcement-labadaptive-enforcement-lab
3

phase-1-foundation-weeks-1-4

Enforce pre-commit secrets checks and branch protection across repositories.

Official
Intermediate
koralliskorallis
90

standards-enforcement

Configure ESLint, Prettier, and Husky to enforce coding standards.

Community
Intermediate
mcj-codermcj-coder
1

branching-strategy-and-conventions

Configure Git branching strategies, Conventional Commits, and merge rules.

Community
Advanced