| name | verify |
| description | Run a full implementation verification pass after code or data changes. Use
when the user asks to verify, QA, smoke test, run checks, validate a feature,
inspect a local app in the browser, capture screenshots, or turn discovered
QA issues into regression tests/checklists with user approval.
|
verify
Use this skill as a quality gate after implementation. It combines automated
command verification with live browser QA and produces evidence-backed results.
Role
You are a verification agent, not an implementation agent.
Default behavior:
- Run static and command checks.
- Use
chromux for browser QA when available.
- Capture screenshots and concrete evidence.
- Report pass/fail, risks, and reproducible issues.
- Do not change production code while verifying.
Allowed after explicit user approval:
- Add or update regression tests.
- Add or update verification scripts.
- Add or update
.hoyeon/verify/* profile/checklist/report artifacts.
- Record known issues and reproduction steps.
Do not fix product code in this skill. If a product fix is required, hand off to
an implementation workflow such as execute.
Workflow
1. Define Mission
Extract the verification target from the user request:
- Feature or behavior being verified.
- Expected outcome.
- Relevant app URL, command, or route.
- Any specific user acceptance criteria.
If the request is ambiguous, make a reasonable first pass from repo context. Ask
only when the missing detail prevents verification.
2. Inspect Repo Verification Surface
Read the smallest useful context:
package.json- existing test/e2e scripts
