project-hook-setup

Install five Claude Code hooks enforcing tests, health, and dependencies.

9|Updated Dec 13, 2025
One-click install
npx skills add https://github.com/ingpoc/SKILLS --skill project-hook-setup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-hook-setup
Source: https://github.com/ingpoc/SKILLS/tree/main/project-hook-setup
Command: npx skills add https://github.com/ingpoc/SKILLS --skill project-hook-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) components.

What problem does it solve?

Per-project Claude Code hooks are often missing when starting a new project, leaving teams without enforcement for tests, health checks, and dependency validation. This skill automatically configures per-project hooks during INIT or when .claude/hooks is absent, installing five templates that read from .claude/config/project.json to enforce project standards.

Core Features & Use Cases

  • Installs five per-project hooks that enforce:
    • Test verification before marking features completed
    • File existence before marking features completed
    • Health checks for API projects
    • Dependency validation
    • Session-entry protocol setup
  • Works during INIT or when creating new projects, and adapts to existing project configurations.
  • Supports both interactive prompts and non-interactive automation; updates .claude/settings.json accordingly.

Quick Start

Run the setup-project-hooks.sh script to install hooks and configure project settings for Claude Code.

Frequently Asked Questions about project-hook-setup

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

FAQPage Schema
How do I set up per-project hooks in Claude Code?▼

Per-project hooks in Claude Code enforce project standards by reading from .claude/config/project.json to verify tests, validate dependencies, and run health checks before features are marked completed.

How do I enforce test verification before marking a feature completed?▼

To enforce test verification before marking a feature completed, install per-project hooks that read configuration from .claude/config/project.json and automatically validate test execution status during your development workflow.

Do I need jq installed to configure project hooks?▼

Yes, jq is a required dependency for setting up project hooks, as the scripts use it to parse configuration from .claude/config/project.json during the automated installation and enforcement process.

Can I automate hook setup non-interactively for new projects?▼

Yes, you can automate hook setup non-interactively for new projects. The setup script supports non-interactive automation to install all five hooks and update .claude/settings.json without requiring manual interactive prompts.

What project standards do the five Claude Code hooks enforce?▼

The five hooks enforce test verification, file existence validation, API health checks, dependency validation, and session-entry protocol setup by reading rules from .claude/config/project.json.

Why are my Claude Code project hooks missing when I start a new project?▼

Claude Code project hooks are missing in new projects because per-project configurations are not initialized by default. Running the setup script installs the five required templates to enforce tests, health, and dependencies.