harness-validate

Scan codebases for CLAUDE.md rule violations before submission.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Taek-D/kbo_appintoss --skill harness-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-validate
Source: https://github.com/Taek-D/kbo_appintoss/tree/main/miniapp/.claude/skills/harness-validate
Command: npx skills add https://github.com/Taek-D/kbo_appintoss --skill harness-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the validation of CLAUDE.md review rules (NEVER/ALWAYS/CONDITIONAL) against a codebase to proactively detect violations and suggest fixes.

Core Features & Use Cases

  • Lightweight automated screening of codebases to surface potential review blockers.
  • Iterative verification loop: detect violations, propose fixes, re-run until all checks pass.
  • Applicable pre-release checks for frontend and backend mini-apps with src/, ensuring compliance before submission.

Quick Start

Run harness-validate against your project to identify rule violations and iterate on fixes until all checks pass.

Frequently Asked Questions about harness-validate

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

FAQPage Schema
How do I validate CLAUDE.md rules across my codebase before submission?

To automate CLAUDE.md rule checks, run a scanner that evaluates NEVER, ALWAYS, and CONDITIONAL directives across your codebase. It flags violations in src/ files and provides a deterministic pass/fail outcome with specific remediation guidance.

What is a CLAUDE.md violation and how does automated detection work?

A CLAUDE.md violation happens when code contradicts NEVER, ALWAYS, or CONDITIONAL project rules. Automated detection scans source files under src/ during QA cycles to identify these breaches deterministically and propose specific fixes.

Can I use automated CLAUDE.md validation for both frontend and backend mini-apps?

Yes, you can use automated CLAUDE.md validation for both frontend and backend mini-apps. The scanner evaluates source code within the src/ directory during QA cycles to enforce rule compliance across both environments.

How do I run an iterative verification loop for CLAUDE.md rule compliance?

Run an iterative verification loop by scanning for CLAUDE.md violations, applying the proposed fixes, and re-running the check until all rules pass. This loop verifies full compliance before pre-release submission.

Do I need external dependencies to run CLAUDE.md pre-release checks?

No external dependencies are required for CLAUDE.md pre-release checks. The validation operates using only your existing project scripts to scan src/ files and produce deterministic pass/fail outcomes.