check

Verify changes against specs at runtime and review diffs with a fresh model before merge.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/JabezJesudasonJena/hack-ag --skill check-jabezjesudasonjena
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check
Source: https://github.com/JabezJesudasonJena/hack-ag/tree/main/.agents/skills/check
Command: npx skills add https://github.com/JabezJesudasonJena/hack-ag --skill check-jabezjesudasonjena

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Green tests do not prove a feature actually works, and a model reviewing its own code shares its own blind spots. This skill closes both gaps before merge: it drives the real application to prove behavior against the spec, and it runs a senior code review on a different model than wrote the code. ## Core Features & Use Cases - Runtime verification: The verify mode launches the real app, exercises the changed flow (UI, API, CLI, or job), and checks every acceptance criterion and specced surface, with an evidence ledger so no verdict is fabricated. - Cross-model code review: The review mode spawns a reviewer subagent on a contrasting model, ranks findings by severity (blocker, major, minor, nit), and writes them to docs/reviews/. - Use Case: After finishing a feature with /develop, run verify to confirm every acceptance criterion is met in the running app, then run review before opening the PR to get a fresh-model senior read of the diff. ## Quick Start Ask the assistant to run the check skill in verify mode on the current branch to prove the change works against its spec before merging.

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 actually works before merging?

Run the check skill in verify mode. It scopes the changed files from git, launches the app using the project's own run command, exercises each observable behavior, and reports pass or fail per acceptance criterion with cited evidence.

How do I get a code review from a different AI model?

Run the check skill in review mode. It detects which model wrote the code, spawns a reviewer subagent on a contrasting model, and writes severity-ranked findings to docs/reviews/ without editing any code.

What is the difference between verify and review modes?

Verify drives the running app to prove behavior matches the spec, catching surfaces that were specced but never built. Review is a static senior read of the diff by a different model, catching correctness, security, and maintainability issues.

Does the check skill work on projects without tests?

Yes. The review mode recognizes a none-by-design test signal where the project gates on typecheck plus runtime verification, and it will not raise missing-test findings. Verify mode serves as the safety net for such projects.

Can the check skill modify my code to fix issues it finds?

No. Both modes are read only on code. Verify points failures at /debug or /develop, and review writes findings for the implementer to fix. The skill never edits application code.