skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
owainlewis/blueprint369 installs

test

Proves a code change works: runs every repository check until green, then proves each acceptance criterion with tests, and by running the real app for anything a user can see or call. Use to test or verify a diff, branch, PR, URL, or user flow.

How do I install this agent skill?

npx skills add https://github.com/owainlewis/blueprint --skill test
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill automates code testing and verification. It is generally safe for its intended purpose but carries a low risk of indirect prompt injection because it executes commands found in repository files and processes external ticket criteria which could contain malicious instructions.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

Test

Show that each acceptance criterion passes. Reading the code is not proof.

Steps

  1. Run every check the repository has: format, lint, typecheck, and tests. The commands are in AGENTS.md, CLAUDE.md, the README, or the project's scripts. Fix what the change broke and run them all again. After three rounds on the same failure, stop and report it.
  2. List each acceptance criterion (AC-n, J-n, REQ-n, INV-n) from the ticket, word for word.
  3. Point each criterion to a test that proves it. Where none exists, write one that calls the public interface. Revert the code once to confirm the main new test fails.
  4. If a user can see or call the change, run the real app the way they would. Use the repository's own end-to-end tests or scripts if it has them. Otherwise use a real browser for a web page, a terminal for a command-line tool, and HTTP requests for an API.
  5. For a web page, check desktop and mobile widths, keyboard use, and console errors.
  6. Save the evidence for the PR: screenshots, terminal output, or responses.

Return

Failures and unverified criteria first:

Criterion: <ID or exact wording>
Result: Pass / Fail / Unverified
Evidence: <command, user flow, screenshot, or captured output>

Then each check command you ran and its result.

Fix the code, not the test. Report failures the change did not cause; leave them alone.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/owainlewis/blueprint/test">View test on skillZs</a>