galahad

Enforce strict tests, types, lints, and coverage standards across TypeScript and Python projects.

74|12|Updated Nov 1, 2024
One-click install
npx skills add https://github.com/AD-SDL/MADSci --skill galahad-ad-sdl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: galahad
Source: https://github.com/AD-SDL/MADSci/tree/main/skills/galahad
Command: npx skills add https://github.com/AD-SDL/MADSci --skill galahad-ad-sdl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It provides a practical framework for enforcing rigorous standards across tests, types, linting, and coverage to improve software reliability and maintainability.

Core Features & Use Cases

  • Establishes consistent rules for test quality, type-safety, lint rules, and coverage signals.
  • Guides teams on when to apply stricter checks and how to balance pragmatism with rigor.
  • Use case: a project migrating from lax testing to Galahad-aligned practices to reduce regressions.

Quick Start

Enable Galahad-guided checks in your project by applying the recommended testing, typing, linting, and coverage standards to your codebase and CI.

Frequently Asked Questions about galahad

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

FAQPage Schema
How do I enforce strict testing standards and improve code quality in TypeScript and Python projects?

Strict testing standards improve code quality by applying consistent rules for tests, type-safety, linting, and coverage signals across TypeScript and Python projects to reduce regressions and increase reliability.

What is the Galahad principle for software quality and when should I apply it?

The Galahad principle establishes rigorous standards for tests, types, lints, and coverage. Apply it when migrating from lax testing to strict practices to enforce safe defaults and gain actionable feedback through green checks.

How do I set up pre-commit hygiene and meaningful coverage signals for my codebase?

Pre-commit hygiene and meaningful coverage signals are established by adopting disciplined rules for linting and testing, ensuring CI pipelines provide actionable feedback and safe defaults before code is merged.

Can I use strict linting and type-safety rules to safely refactor a real-world codebase?

Strict linting and type-safety rules guide disciplined refactoring in real-world codebases by providing well-defined project standards and actionable feedback, ensuring safe transitions during migration from lax practices.

What's the best way to balance pragmatism with rigor when adopting strict testing and type checks?

Balancing pragmatism with rigor involves applying strict checks for tests, types, and lints gradually, guiding teams on when to enforce stricter rules while maintaining safe defaults and meaningful coverage signals.