galahad

Enforce testing discipline and type safety in code reviews and CI gates.

10|2|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/lambdamechanic/tooltest --skill galahad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: galahad
Source: https://github.com/lambdamechanic/tooltest/tree/main/skills/galahad
Command: npx skills add https://github.com/lambdamechanic/tooltest --skill galahad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill codifies testing standards inspired by the Galahad Principle to help teams avoid ambiguous feedback and unchecked risks in software projects.

Core Features & Use Cases

  • Enforces emphasis on type safety, clear failure signals, and comprehensive coverage discipline.
  • Clarifies expectations for code quality and measurement, guiding CI and reviews.
  • Use Case: apply during code reviews or CI gates to ensure every change meets strict quality criteria.

Quick Start

Integrate the Galahad rules into your project governance and start enforcing strict type-safety checks, maximize test coverage, and review feedback until all checks pass.

Frequently Asked Questions about galahad

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

FAQPage Schema
How do I enforce type safety and prevent coverage gaming in CI pipelines?

You can enforce type safety and prevent coverage gaming by applying strict testing discipline rules as CI gates, prohibiting unsafe patterns like type escapes and silent failures to ensure verifiable test coverage.

What is the Galahad Principle for software testing standards?

The Galahad Principle for software testing codifies standards to help teams avoid ambiguous feedback and unchecked risks by enforcing strict type safety, clear failure signals, and comprehensive coverage discipline during code reviews.

How do I prevent silent test failures during code reviews?

To prevent silent test failures during code reviews, integrate testing rules that enforce clear failure signals and prohibit ambiguous feedback, ensuring every change meets strict code quality criteria.

What are the limitations of enforcing strict test coverage rules?

Strict test coverage rules require a SKILL.md file with name and description frontmatter, and teams must review feedback until all checks pass, which may slow down development velocity for projects not ready for strict governance.

Do I need a specific configuration file to apply code quality checks?

Yes, you need a SKILL.md file with name and description frontmatter to apply these code quality checks, which integrate into project governance to enforce strict type-safety and maximize test coverage.