check

Verify running app behavior against spec done-when criteria with captured evidence.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/LeroyAdonis/kitfix-2.0 --skill check-leroyadonis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: check
Source: https://github.com/LeroyAdonis/kitfix-2.0/tree/main/.agents/skills/check
Command: npx skills add https://github.com/LeroyAdonis/kitfix-2.0 --skill check-leroyadonis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? A green build only proves code compiles; it does not prove the feature actually behaves the way the spec promised. This Skill closes that gap by running the real application and checking each observable "done when" criterion from the current feature spec, producing evidence-backed pass/fail results before work is marked complete. ## Core Features & Use Cases - Spec-Driven Checklist: Reads blueprint/context/current-feature.md and converts every "done when" criterion into a concrete, observable claim to verify. - Real App Verification: Drives the actual running app — browser routes for web apps, commands for CLIs, endpoints for servers — capturing screenshots, output, console errors, and failed network requests as evidence. - Honest Reporting: Reports one line per criterion as pass, fail, or skip, never edits source or commits, and hands failures back to /implement with named fixes. - Use Case: After implementing a PDF download feature, run the check to confirm clicking the button actually downloads certificate-<slug>.pdf, loading states render, and no console errors appear — before declaring the feature complete. ## Quick Start Ask the agent to run /check on the current feature to verify every done-when criterion in the spec against the running app.

Frequently Asked Questions about check

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

FAQPage Schema
How do I verify a feature works before marking it complete?▼

Run the check skill, which reads the done-when criteria from current-feature.md, starts the real app, exercises each criterion through actual interaction, and reports evidence-backed pass or fail verdicts per item.

What is the difference between a passing build and behavioral verification?▼

A passing build only proves code compiles. Behavioral verification runs the actual app and confirms observable outcomes like downloads, route responses, and UI flows, capturing screenshots and output as proof.

Does the check skill use Playwright for browser testing?▼

It prefers Playwright for browser driving, screenshots, and console error checks when Playwright is already installed or declared in AGENTS.md. If not installed, it uses another real-browser evidence path and reports what was used.

Can the check skill fix failures it finds?▼

No. It only observes and reports; it never edits source, commits, or merges. Failed criteria are handed back to the /implement step with specific notes on what to fix.

What happens when a criterion cannot be verified locally?▼

The criterion is reported as skipped with an explanation of why it could not be verified, such as requiring a deployed environment. It is never reported as a pass without evidence.