agentsclimarketplace
Sign in

Verify software change

Skill ImYourBoyRoy/agent-continuity-stack/skills/verify-software-change

Design and run risk-based verification after software or infrastructure changes, or when asked whether work is fixed or ready. Respect repository-specific remote, hardware, staging, and production constraints.From its SKILL.md

Install
npx -y skills add ImYourBoyRoy/agent-continuity-stack --skill verify-software-change

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 14 days oldThe repository was created 14 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.3 KB, 405 tokens by cl100k_base, as published. Nobody here has run it

Verify Software Change

Build the smallest sufficient evidence chain for the actual risk.

Define the claim

Before running checks, state what must be true. Map each material change to:

  • expected behavior
  • likely regression surface
  • appropriate evidence
  • environment required

Read references/risk-matrix.md for selecting depth. Do not substitute broad but irrelevant test volume for targeted evidence.

Follow project constraints

Read repository instructions and use approved commands. Preserve remote-only, hardware-bound, sandboxed, staging, production, or resource constraints. Do not install tools, deploy, access production, or broaden permissions merely to make verification convenient.

Execute progressively

  1. inspect static consistency and affected references
  2. run focused formatter, lint, type, schema, or unit checks
  3. test the changed behavior and important failure paths
  4. broaden to subsystem, build, packaging, or integration checks when risk warrants it
  5. use preview, staging, device, or production evidence only when authorized
  6. inspect exit status and relevant output
  7. classify existing versus introduced warnings and failures

After refactors, check imports, signatures, generated bindings, configuration, entry points, tests, examples, and documented commands.

Preserve evidence integrity

  • Never fabricate output or convert inspection into an execution claim.
  • Do not hide failed attempts or warnings.
  • Do not weaken tests to make them pass unless the changed expectation is explicitly correct and reviewed.
  • Do not discard unrelated work to obtain a clean state.
  • Label local, remote, simulated, preview, staging, device, and production evidence.
  • If a check cannot run, explain why and choose the best non-equivalent evidence without calling it equivalent.

Report

Provide:

  • claim evaluated
  • commands and environments
  • passed behavior
  • warnings and failures
  • existing versus introduced issues
  • areas inspected but not executed
  • remaining uncertainty
  • readiness conclusion bounded by the evidence

What ships with it: 3 files

1.6 KB alongside SKILL.md

agents/

references/

Keep looking

Skills are one crate of 326,834. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.