validate-parser

Compare SpecVital parser test counts against framework CLI ground truths.

1|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/kubrickcode/specvital --skill validate-parser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-parser
Source: https://github.com/kubrickcode/specvital/tree/main/.claude/skills/validate-parser
Command: npx skills add https://github.com/kubrickcode/specvital --skill validate-parser

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill ensures the accuracy of the SpecVital Core parser by comparing its test detection results against the actual test counts reported by framework CLIs, identifying and helping to fix parser bugs.

Core Features & Use Cases

  • Automated Validation: Compares SpecVital's test count with ground truth from framework CLIs.
  • Bug Detection: Identifies discrepancies indicating parser inaccuracies.
  • Use Case: When a new version of a test framework is released, use this Skill to validate that SpecVital's parser correctly detects all tests in a sample repository, ensuring compatibility and accuracy.

Quick Start

Validate the SpecVital parser against the 'axios' GitHub repository.

Frequently Asked Questions about validate-parser

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

FAQPage Schema
How do I validate parser accuracy against a test framework CLI?

Parser validation compares detected test counts against actual test counts from framework CLIs by cloning target repositories, executing CLI commands for ground truth, running the parser, and generating a detailed discrepancy report.

What is parser validation and when do I need it for bug detection?

Parser validation is the process of verifying test detection accuracy by comparing parser results with framework CLI ground truth. You need it after test framework releases to ensure compatibility and identify parser bugs causing test count discrepancies.

Can I validate a specific GitHub repository like axios for test detection accuracy?

Yes, you can validate specific GitHub repositories like axios through explicit repository requests. The process clones the repository, executes framework-specific CLI commands, compares results with parser output, and reports any test detection discrepancies.

Do I need to manually select repositories for parser validation?

No, manual selection is not required. For implicit requests, the skill automatically selects repositories not listed in repos.yaml, while explicit requests allow you to target specific repositories for parser accuracy validation against framework CLIs.

What are the limitations of using CLI comparison for parser bug detection?

CLI comparison for bug detection requires cloning repositories and relies on framework-specific CLI commands for ground truth. Limitations include potential discrepancies if the parser and CLI interpret test definitions differently within the generated report.