validation

Coordinate cross-phase validation pipelines with Pass/Fail/Warn strictness.

2|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/Nickalus12/Loom --skill validation-nickalus12
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validation
Source: https://github.com/Nickalus12/Loom/tree/main/claude/skills/validation
Command: npx skills add https://github.com/Nickalus12/Loom --skill validation-nickalus12

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-cutting validation methodology to verify phase outputs and preserve project integrity during orchestration.

Core Features & Use Cases

  • Establishes a repeatable validation pipeline across builds, tests, and quality checks.
  • Supports manual verification with a structured checklist for non-automatable validations.
  • Provides guidance for interpreting results and applying corrective actions to maintain quality.

Quick Start

Run the validation pipeline after each phase to verify that outputs meet the defined quality gates.

Frequently Asked Questions about validation

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

FAQPage Schema
How do I automate quality checks across project phases?

Automate quality checks by running a multi-step validation pipeline that coordinates build, lint, unit tests, and integration tests to verify phase outputs and maintain project integrity.

What is cross-phase validation in a build pipeline?

Cross-phase validation is a methodology that verifies outputs after each orchestration phase, enforcing strict quality gates using a Pass, Fail, or Warn strictness model to preserve project integrity.

How do I run standalone lint and unit tests on an existing codebase?

Run standalone validation checks directly across your codebase to execute the defined lint and unit test pipeline, ensuring outputs meet the established quality gates without requiring full orchestration.

How do I configure validation strictness to warn instead of fail?

Configure validation strictness by setting the LOOM_VALIDATION_STRICTNESS variable, which controls the quality gate model to return Pass, Fail, or Warn results based on your pipeline requirements.

Can I use a manual checklist for non-automatable integration tests?

Yes, you can use a structured manual verification checklist to handle non-automatable integration tests, providing guidance for interpreting results and applying corrective actions to maintain quality.