sdd-verify

Run tests and builds to generate structured verification reports.

Updated Nov 19, 2024
One-click install
npx skills add https://github.com/Strocs/.dotfiles --skill sdd-verify-strocs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-verify
Source: https://github.com/Strocs/.dotfiles/tree/main/.config/opencode/skills/sdd-verify
Command: npx skills add https://github.com/Strocs/.dotfiles --skill sdd-verify-strocs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifying that code changes align with specifications by executing the changes and collecting verifiable evidence of correctness.

Core Features & Use Cases

  • End-to-end verification: executes changes, runs tests, and builds to prove compliance with specs.
  • Evidence-driven reports: generates a structured verification report suitable for audits.
  • Risk-aware validation: flags incomplete or failing scenarios and provides remediation guidance.

Quick Start

Ask the sdd-verify tool to validate a completed change and produce a verification report.

Frequently Asked Questions about sdd-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify code changes against specifications with runtime evidence?

To verify code changes against specifications, execute the completed changes alongside builds and tests to produce a structured report proving compliance. This enforces an execution-based verification contract.

What is execution-based verification for code changes?

Execution-based verification is the process of running builds and tests against code changes to validate correctness and completeness. It generates structured, audit-ready evidence demonstrating that the code aligns with specifications.

How do I generate an audit-ready verification report for a completed build and test cycle?

You can generate an audit-ready verification report by running an end-to-end validation on the completed change. The tool produces a structured document containing evidence of correctness, compliance, and safety.

Does end-to-end verification work across different project toolchains?

Yes, end-to-end verification applies across projects and toolchains to verify completeness, correctness, and safety in code changes. It standardizes the validation process regardless of the specific build environment.

What happens when a runtime test fails during code verification?

When a runtime test fails during code verification, the process flags the incomplete or failing scenarios and provides specific remediation guidance. This risk-aware validation helps identify and resolve safety issues.