add-tool

Create a QA tool Job in GitHooks with registry registration and tests.

9|Updated Apr 12, 2020
One-click install
npx skills add https://github.com/Wtyd/githooks --skill add-tool-wtyd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-tool
Source: https://github.com/Wtyd/githooks/tree/main/.claude/skills/add-tool
Command: npx skills add https://github.com/Wtyd/githooks --skill add-tool-wtyd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a complete guide to adding a new QA tool to GitHooks by implementing it as a Job in the src/Jobs/ directory, enabling standardized tool support across projects.

Core Features & Use Cases

  • Step-by-step instructions to create the Job class, register it in the JobRegistry, declare development dependencies, write tests, and wire it into QA configurations.
  • Includes validation steps and examples to ensure the tool builds, runs, and integrates with existing qa flows.
  • Use Case: When teams want to add support for a new code-analysis tool (e.g., phpstan, psalm, phpinsights) and have GitHooks manage it as a first-class Job.

Quick Start

Create a new Tool Job following the pattern described and wire it into qa/githooks.php.

Frequently Asked Questions about add-tool

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

FAQPage Schema
How do I add a new QA tool to GitHooks as a Job?

To add a new QA tool to GitHooks, you create a Job class in the src/Jobs/ directory, register it in the JobRegistry, declare dev-dependencies, write tests, and wire it into QA configurations for standardized tool support.

What steps are required to register a code-analysis tool in a PHP workflow?

Registering a code-analysis tool requires creating the Job class, adding it to the JobRegistry, declaring development dependencies, running tests, and updating QA configurations to validate the tool builds and integrates with existing flows.

Can I integrate tools like phpstan or psalm into GitHooks as first-class Jobs?

Yes, you can integrate code-analysis tools like phpstan, psalm, or phpinsights into GitHooks by implementing them as a Job to manage them as first-class workflow components across projects.

What is the best way to declare dev-dependencies for a new QA tool Job?

The best way to declare dev-dependencies for a QA tool Job is to follow the step-by-step implementation guide, ensuring the dependency declarations align with the tool registration and QA configuration updates.

Why does a newly added QA tool Job need validation in GitHooks?

A newly added QA tool Job needs validation to ensure the tool builds, runs correctly, and integrates seamlessly with existing QA flows, enforcing end-to-end tooling requirements including tests and configuration checks.

Do I need to update qa/githooks.php when adding a new tool Job?

Yes, you need to update qa/githooks.php to wire the new Tool Job into the QA configurations, ensuring the code-analysis tool is properly integrated into the standardized workflow.