galahad

Assess tests, types, and linting to guide incremental codebase improvements.

Updated Dec 31, 2025

Search Tags:#testing #practice #code-quality #type-safety #lint #galahad #principle

Ready to run

npx skills add https://github.com/RyanTheRobothead/skills --skill galahad-ryantherobothead

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: galahad
Source: https://github.com/RyanTheRobothead/skills/tree/main/skills/galahad
Command: npx skills add https://github.com/RyanTheRobothead/skills --skill galahad-ryantherobothead

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Achieving consistently green checks across tests, types, and linting can be difficult; teams struggle to build trust in code quality when failures appear unpredictably.

Core Features & Use Cases

Assessment framework: Evaluate current test coverage, type strictness, and lint status across languages.
Guided standard discovery: Identify existing project standards and adapt Galahad rules pragmatically to the codebase.
Safe, incremental improvements: Propose non-blocking refactors that raise quality without breaking user goals.
Use Case: In a mixed TypeScript/Python repo with legacy tests, apply the Galahad principle to move toward full green status over time.

Quick Start

Compose a plan to audit tests, types, and lint rules across the project and begin applying all-green safeguards.

Frequently Asked Questions about galahad

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

FAQPage Schema

How do I get all-green checks consistently across tests, types, and linting in a legacy codebase?▼

Achieving all-green checks requires a formal assessment framework that evaluates current coverage, type strictness, and lint status, then proposes safe, incremental refactors that raise code quality without breaking existing functionality.

What is the best way to improve type safety and test coverage without breaking existing user goals?▼

Improving type safety and coverage safely involves frontmatter-driven guardrails that guide non-blocking, incremental refactors, ensuring quality improvements are applied pragmatically without disrupting current project standards or functionality.

Can I apply code quality and lint standards to a mixed TypeScript and Python repository?▼

Yes, code quality and lint standards can be applied across mixed TypeScript and Python repositories by discovering existing project standards and adapting assessment rules pragmatically to guide improvements across diverse codebases.

How do I audit test coverage, type strictness, and lint status across a multi-language project?▼

Auditing test coverage, type strictness, and lint status involves composing a plan that evaluates current checks across the project, identifying existing standards, and applying all-green safeguards incrementally over time.

Why do unpredictable test, type, and lint failures keep appearing in my builds?▼

Unpredictable build failures appear when teams lack a formalized assessment framework and standardized guardrails, making it difficult to build trust in code quality and address type safety, coverage, and lint issues consistently.

Are there limitations to incrementally refactoring toward full green status in diverse codebases?▼

Incremental refactoring toward full green status is limited by the need to identify existing project standards first; improvements must be non-blocking and adapted pragmatically to avoid breaking user goals during the transition.