tapps-validate

Validate changed files against per-file quality thresholds before completion.

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/wtthornton/tapps-brain --skill tapps-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tapps-validate
Source: https://github.com/wtthornton/tapps-brain/tree/main/.claude/skills/tapps-validate
Command: npx skills add https://github.com/wtthornton/tapps-brain --skill tapps-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate changed files meet quality thresholds before declaring work complete.

Core Features & Use Cases

  • Validate individual changed files for a pass/fail status with per-file scoring to enforce code quality gates.
  • Enforce explicit file_paths to scope evaluation, preventing slow or unintended scans.
  • Integrates with the MCP workflow to ensure changes meet project quality gates before merge and review.

Quick Start

Run mcp__tapps-mcp__tapps_validate_changed with explicit file_paths scoped to the changed files.

Frequently Asked Questions about tapps-validate

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

FAQPage Schema
How do I validate code quality for changed files before a merge?

You validate changed files by supplying explicit file paths to the validator tool, which enforces per-file quality scores and pass/fail statuses. This ensures completion occurs only when all changed files pass their quality thresholds.

What is the best way to enforce quality gates on changed files in a CI workflow?

Enforcing quality gates involves integrating an MCP validation tool that scopes evaluation to explicitly identified changed files. This prevents slow or unintended scans and ensures changes meet project quality thresholds before review.

How do I identify and scope evaluation to only the changed files in my session?

You scope evaluation by identifying the changed files in your session and supplying their explicit file paths to the validator. This targeted approach prevents slow or unintended scans across the entire codebase.

Does the validator require explicit file paths to check code quality?

Yes, the validator requires explicit file paths to scope evaluation. Supplying explicit file paths ensures the tool only checks the specific changed files, preventing slow or unintended full codebase scans.

Why does code validation fail even when some changed files pass quality thresholds?

Code validation fails because the tool ensures completion only when all changed files pass. It enforces per-file scores and pass/fail statuses, meaning a single failing file prevents the overall work from being declared complete.