← Explore all skills

SECURITY / trailofbits

Specification to Code Compliance

Compare authoritative requirements with implementation evidence and retain undecidable or unchecked requirements.

“Check code against the documentation that specifies it - which requirements hold, which the code contradicts, which are absent, and what the code does that”

01 / THE REASONING

Why this made the selection.

  • The skill compares code with a document that says what the code is supposed to do. It is not a general bug hunt, and it is not a documentation rewrite.
  • The rubric sets severity by consequence, not by how far the wording and the code diverged.
  • The definition uses six implementation verdicts and independent code/document refutation, with explicit reporting for unreadable and unverified inputs.
  • Audit a protocol or contract implementation against its actual specification

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • plugins/spec-to-code-compliance/skills/spec-to-code-compliance/SKILL.md
  • plugins/spec-to-code-compliance/skills/spec-to-code-compliance/resources/DIVERGENCE_RUBRIC.md
  • LICENSE
  • README.md

Our findings

  • Tools are local reads plus the workflow. It writes spec-compliance/REPORT.md and one file per requirement. It does not fetch the specification from the network by itself.
  • It does not apply when there is no document of intended behaviour, and it does not look for bugs both artefacts are silent about.
  • The workflow section says it does not make the severity judgment for you. The rubric ties that judgment to consequence, not to how far the words and the code diverged.
  • The definition uses six implementation verdicts and independent code/document refutation, with explicit reporting for unreadable and unverified inputs.

Not established by this review

  • The resource was not executed and its tools were not called.
  • The compliance workflow was not dispatched and no report was written.
  • No skill execution, authenticated service operation, or outcome benchmark was performed.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Add a skill to your workflow.

Upstream setup instructions ↗
  1. Check out trailofbits/skills at 8e54050ae63c2f62224c35b1616efe71865b4777 and install the complete spec-to-code-compliance plugin through the publisher-supported host workflow, retaining sibling agents, workflows, scripts and references.
  2. Provide specification and code paths, scope and requirement limit; retain the complete plugin.
  3. Inspect the requirements inventory and unverified/notChecked sections with REPORT.md; review consequences of deviations rather than wording alone.

Before you start

  • A local checkout and the tools required by the selected workflow

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. Pinned skill definition ↗Checked

    https://github.com/trailofbits/skills/blob/8e54050ae63c2f62224c35b1616efe71865b4777/plugins/spec-to-code-compliance/skills/spec-to-code-compliance/SKILL.md

    Supports: summary, whySelected, bestFor, limitations, install, access, review

  2. https://github.com/trailofbits/skills/blob/8e54050ae63c2f62224c35b1616efe71865b4777/README.md

    Supports: install

  3. CC-BY-SA-4.0 licence ↗Checked

    https://github.com/trailofbits/skills/blob/8e54050ae63c2f62224c35b1616efe71865b4777/LICENSE

    Supports: license

Evidence & Ask