Verify software implementations against dx declaration contracts via black-box testing.
npx skills add https://github.com/dewitt/dx --skill judge-dewitt
Please help me install this Agent Skill. Skill: judge Source: https://github.com/dewitt/dx/tree/main/skills/judge Command: npx skills add https://github.com/dewitt/dx --skill judge-dewitt
This skill resolves the ambiguity between software specifications and their actual implementations by providing a rigorous, black-box verification process that identifies whether failures stem from implementation bugs or gaps in the specification itself.
Use the judge skill to verify the implementation against the system.md declaration and generate a formal judgement report.
High-intent search queries and answers about installing and using this skill.
To verify implementation conformance to specifications, execute every defined contract in a declaration as a black-box test to ensure the software meets all requirements. This process systematically classifies failures into implementation bugs or specification gaps.
Black-box contract testing for software compliance validates target implementations against declared requirements without inspecting internal code. It executes defined contracts externally, categorizing any resulting failures as either implementation bugs or gaps within the specification.
Yes, you need the dx toolchain to run contract verification. The verification process requires the dx toolchain specifically to enumerate declared contracts and execute them against the target implementation during the audit.
To generate an audit trail for software specification compliance, run a verification process against your declarations to produce a version-controlled JUDGEMENT.md file. This file serves as an immutable record of conformance for specific commits.
Contract testing reports specification gaps alongside bugs because failures often stem from incomplete requirements rather than code errors. Systematically classifying failures into implementation bugs or spec gaps ensures the correct team receives the remediation task.
The best way to classify test failures during specification audits is systematic categorization into implementation bugs or specification gaps. This black-box testing approach ensures targeted remediation by directing fixes to the appropriate engineering or specification teams.
dewittGenerate and modify source code to satisfy dx declaration specifications.
DojoGenesisAudit a codebase against a formal specification and generate a GAPS.md registry.
CENKSSSAutomate iterative quality assurance loops for test execution and coverage analysis.
BellaBeGenerate Lean 4 proofs for categorical laws and verification reports.
