agentsclimarketplace
Sign in

Openspec verify change

Skill TheSmuks/openspec-hermes/skills/openspec/openspec-verify-change

Use when working with OpenSpec in Hermes: check implementation completeness, correctness, coherence, and evidence before archive.From its SKILL.md

Install
npx -y skills add TheSmuks/openspec-hermes --skill openspec-verify-change

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

One thing to look at

  • 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.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.9 KB, 347 tokens by cl100k_base, as published. Nobody here has run it

openspec-verify-change

Use this for OpenSpec's /opsx:verify workflow.

Hermes operating rules for OpenSpec

  • Work from the user's project root. If unknown, inspect the current directory first.
  • Ensure the OpenSpec CLI exists before using it: openspec --version. If missing, install with npm install -g @fission-ai/openspec@latest.
  • Initialize projects with openspec init --tools none unless the user also wants other AI-tool integrations. Hermes uses these skills, not OpenSpec-generated slash commands.
  • Prefer agent-compatible OpenSpec CLI calls with --json where available: openspec list --json, openspec status --change <id> --json, openspec instructions <artifact> --change <id> --json, openspec validate --all --json.
  • Read generated artifacts before editing or implementing. Do not invent OpenSpec state.
  • Run validation after changing OpenSpec artifacts: openspec validate <change> or openspec validate --all.
  • Keep changes focused. If user scope diverges, update the existing change only when intent is the same; otherwise create a new change.

Procedure

  1. Identify the target change.
  2. Read all change artifacts and main specs touched by the change.
  3. Run openspec validate <name>.
  4. Search the codebase for evidence for every task, requirement, and scenario.
  5. Run relevant tests or build commands.
  6. Report CRITICAL issues, WARNINGs, and SUGGESTIONs.
  7. State whether the change is ready to archive.

Verification dimensions: completeness, correctness, and coherence.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most quality gates skills give in 347 tokens

Counted across 1,195 of the 2,094 authors here whose files we hold, read 2026-08-07

  • Read the output and check the exit codein 54 of 1195, across 14 files
  • Verify requirements using a line-by-line checklistin 53 of 1195, across 12 files
  • Identify the verification command proving the claimin 51 of 1195, across 12 files
  • Run the full verification commandin 50 of 1195, across 11 files
  • Verify output confirms the claimin 49 of 1195, across 12 files
  • Check version control diff after agent delegationin 46 of 1195, across 6 files
  • State claim with evidencein 44 of 1195, across 4 files
  • Run the test suitein 33 of 1195, across 26 files
  • Keep state in memory by defaultin 27 of 1195, across 6 files
  • Make prototype runnable with one commandin 26 of 1195, across 5 files
  • Produce a verification reportin 25 of 1195, across 14 files
  • Detect the package manager from lockfilesin 24 of 1195, across 5 files

Said here and by no other author read

  • work from the user's project root
  • ensure openspec cli exists before using it
  • initialize projects with openspec init
  • prefer agent-compatible openspec cli calls with json
  • read generated artifacts before editing or implementing
  • run validation after changing openspec artifacts

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

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.