verification-specialist

Adversarially verify CG-agent-harness changes through executed tests and negative probes without modifying the project.

Updated Sep 7, 2026
One-click install
npx skills add https://github.com/cgfixit/CG-agent-harness --skill verification-specialist-cgfixit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-specialist
Source: https://github.com/cgfixit/CG-agent-harness/tree/main/.claude/skills/verification-specialist
Command: npx skills add https://github.com/cgfixit/CG-agent-harness --skill verification-specialist-cgfixit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code review based on reading diffs often misses real defects because claims of correctness go untested. This Skill independently verifies a supplied change to the CG-agent-harness by actually running tests and hostile probes, producing evidence-backed PASS/FAIL verdicts instead of storytelling. ## Core Features & Use Cases - Adversarial verification: Attempts to break a supplied change with at least one negative probe (hostile argv, missing confirm, non-loopback Host, CSRF absent, jail escape) before any PASS verdict. - Surface-mapped evidence: Maps change classes (HTTP guards, shim whitelist, write-refused paths, clone sandbox, config gates, live serve, Chrome browser, desktop packaging) to the specific locking tests that prove or break them. - Structured verdict reporting: Emits per-check command/output/result blocks plus exactly one overall verdict of PASS, FAIL, or PARTIAL, with PARTIAL reserved for checks that could not run. - Use Case: After a teammate patches the harness CSRF guard, invoke this Skill to run tests/auth_guards.rs, probe a request without a CSRF token, and report a verdict with verbatim command output. ## Quick Start Ask the agent to adversarially verify the supplied CG-agent-harness change set, listing the files touched and the original task, and require executed command output for every claimed check.

Frequently Asked Questions about verification-specialist

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

FAQPage Schema
How do I adversarially verify a code change instead of just reviewing it?▼

Run the narrowest locking tests for the change, then execute at least one negative probe such as hostile argv, a missing confirm flag, or a non-loopback Host header. Require verbatim command output for every PASS claim and report a single PASS, FAIL, or PARTIAL verdict.

What is the difference between verification-specialist and cgagentharness-verify?▼

verification-specialist adversarially tries to break a supplied change set and forbids any project mutation. cgagentharness-verify owns the smoke and acceptance bar and may drive documented verify scripts as an operator.

Can this Skill modify the repository or run git commands during verification?▼

No. It forbids creating, editing, or deleting files under the repo and prohibits git add, commit, push, checkout, and rebase. Short-lived probes may use /tmp or $TMPDIR but must be cleaned up afterward.

When should a verification verdict be PARTIAL instead of PASS or FAIL?▼

PARTIAL applies only when required checks cannot run at all, such as a missing Chrome or desktop toolchain for flake-prone acceptance tests. It is never used for uncertainty, and PASS covers only the explicitly stated scope.

Why does live serve smoke testing require a unique port and temp home?▼

An owned temp CGAGENTHARNESS_HOME and unique port prevent confusing the binary under test with another server already bound to the default port 8790. This ensures the smoke evidence actually exercises the supplied change.