add-validation

Create validation branches with auto-detected numbers and run tests.

Updated Dec 4, 2025
One-click install
npx skills add https://github.com/Speculative/debugging-study --skill add-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-validation
Source: https://github.com/Speculative/debugging-study/tree/main/.claude/skills/add-validation
Command: npx skills add https://github.com/Speculative/debugging-study --skill add-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamline the process of creating controlled debugging challenges by automatically generating validation branches tied to a project and numbering system, enabling reproducible test scenarios.

Core Features & Use Cases

  • Auto-detect next available <project>-validation<N> branch from an existing project branch
  • Enforce a deterministic workflow to verify state, create branch, and run tests
  • Support educational and validation tasks by introducing a single, realistic bug for autopsy analysis

Quick Start

Run the add-validation workflow on an existing project branch to create a new validation branch and run the test suite.

Frequently Asked Questions about add-validation

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

FAQPage Schema
How do I create validation branches for debugging scenarios in git?

Creating validation branches involves auto-detecting the next available validation number from a project branch, then enforcing a deterministic workflow to verify state, create the branch, introduce a bug, run tests, and document outcomes.

What is a deterministic validation workflow for introducing bugs?

A deterministic validation workflow is a controlled process that verifies repository state, creates a numbered branch, injects a single realistic bug, runs the test suite, and safely documents the latent bug for educational autopsy analysis.

Can I use this branching workflow on any existing project branch?

Yes, you can apply this workflow to any existing project branch. It auto-detects the next available validation number to simulate real debugging challenges and validate test outcomes reproducibly.

How do I simulate real debugging challenges for educational testing?

You simulate debugging challenges by creating a validation branch from an existing project, introducing a single realistic bug, running the test suite, and performing an autopsy analysis on the resulting test failures.

What's the best way to auto-number validation branches for test autopsy?

The best way to auto-number validation branches is using a workflow that identifies the next available validation number from existing project branches, ensuring deterministic numbering for reproducible test scenarios.