redsub-validate

Run sequential linting, type checking, and unit tests with a 5-step evidence gate.

2|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/redsub-captain/redsub-claude-code --skill redsub-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: redsub-validate
Source: https://github.com/redsub-captain/redsub-claude-code/tree/main/skills/redsub-validate
Command: npx skills add https://github.com/redsub-captain/redsub-claude-code --skill redsub-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the crucial process of validating code quality by running linters, type checkers, and unit tests, ensuring consistency and catching errors early.

Core Features & Use Cases

  • Sequential Validation: Executes linting, type checking, and unit tests in order, stopping on the first failure.
  • SSOT Consistency: Verifies that consumers of canonical sources (configs, types) remain synchronized.
  • Evidence-Based Verification: Enforces a strict 5-step process to ensure all claims are backed by verifiable output.
  • Use Case: Before merging a new feature, run this skill to guarantee the code adheres to project standards, is free of type errors, and all tests pass, providing a clear report of the validation status.

Quick Start

Run the redsub-validate skill to check the current codebase.

Frequently Asked Questions about redsub-validate

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

FAQPage Schema
How do I automate code validation to run linting, type checking, and unit tests sequentially?

Automated code validation runs linters, type checkers, and unit tests sequentially, stopping on the first failure. It detects your package manager and infers validation commands from CLAUDE.md or package.json scripts to execute checks.

What is SSOT consistency checking and how does it verify configuration synchronization?

SSOT consistency checking verifies that consumers of canonical sources like configs, types, and internationalization files remain synchronized. It enforces a strict 5-step evidence gate ensuring all claims are backed by verifiable output.

Can I run code quality validation if my project only has package.json scripts defined?

Yes, code quality validation works if your project only defines package.json scripts. The tool automatically detects the package manager and infers the correct linting, type checking, and testing commands from your existing configurations.

What is the best way to ensure code adheres to project standards before merging a new feature?

The best way to ensure code adheres to project standards before merging is running sequential validation. This process catches type errors and enforces SSOT consistency across configurations, guaranteeing all tests pass with evidence-based verification.

Why does validation stop on the first failure during linting and type checking?

Validation stops on the first failure to provide a clear, targeted report of the codebase status. This sequential execution model prevents cascading errors and enforces an evidence-based 5-step process where every claim requires verifiable output.