feature-verifier

Diagnoses test failures from Feature Swarm verification and outputs a JSON report.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/pcortes/swarm-attack --skill feature-verifier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-verifier
Source: https://github.com/pcortes/swarm-attack/tree/main/default-skills/verifier
Command: npx skills add https://github.com/pcortes/swarm-attack --skill feature-verifier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the diagnosis of test failures during the verification phase, providing immediate root cause analysis and suggesting specific code fixes. This dramatically reduces debugging time, allowing AI agents to self-correct and iterate faster, or clearly escalate when human intervention is truly needed, saving developer effort.

Core Features & Use Cases

  • Automated Failure Diagnosis: Pinpoints the exact reason for test failures, such as missing imports, logic errors, or incorrect parameter usage.
  • Recoverability Assessment: Determines if a fix can be automatically applied by a Coder agent or if the issue requires human oversight due to architectural or environmental problems.
  • Actionable Fix Suggestions: Provides precise code changes and identifies affected files to resolve recoverable issues, enabling quick resolution.
  • Use Case: A newly implemented feature fails its tests. This Skill analyzes the test output, identifies an AssertionError due to incorrect logic in an add function, and suggests changing return a - b to return a + b, enabling an automatic retry and successful verification.

Quick Start

Analyze the provided test output from a failed verification run and suggest specific code changes needed to fix the issue.

Frequently Asked Questions about feature-verifier

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

FAQPage Schema
How do I diagnose why my tests are failing?

Test failure diagnosis identifies the root cause by analyzing test output to pinpoint exact issues like missing imports, logic errors, or incorrect parameters. This Skill examines unit, integration, and end-to-end test failures to determine what went wrong and whether the problem is automatically recoverable or requires human intervention.

Can I get automated suggestions to fix test failures?

Yes. This Skill analyzes failed test output and suggests specific code changes needed to resolve recoverable issues, identifying affected files and the exact modifications required. For example, it might detect an AssertionError in a function and recommend changing the logic to fix the failure.

How do I know if a test failure can be automatically fixed?

The Skill assesses recoverability by evaluating whether a failure stems from issues that can be automatically corrected—such as typos, missing imports, or off-by-one errors—or if it requires human oversight due to architectural or environmental constraints.

What types of test failures can be diagnosed?

This Skill handles failures from unit, integration, and end-to-end tests spanning syntax errors, logic problems, environment issues, and dependency problems. It produces a structured JSON report with root cause, recoverability status, suggested fixes, and affected files.

What output does the Skill provide after analyzing a failure?

The Skill generates a JSON report containing the root cause analysis, recoverability determination, actionable code fix suggestions, and a list of affected files, enabling either automatic retry or informed human intervention.

When should I use automated failure diagnosis versus manual debugging?

Use automated diagnosis when you need rapid iteration during verification phases—it saves debugging time by immediately identifying syntax, logic, environment, and dependency issues. Manual debugging becomes necessary when the Skill determines a failure is not automatically recoverable due to architectural constraints.