MattTheCoder556
UserClaude Code plugin: verify and validate a software build, and compare a rewrite against the build it replaces — user requirements, endpoint-oriented tests, validation records and defect reconciliation. Citations are opened and line-checked, counts are computed, and each skill refuses what it cannot support.
Categories
Indexed Skills (5)
swbugs
Reconcile a project's outstanding defects across two builds of the same software — typically a legacy build and its rewrite — and say, for each one, whether it is still open, migrated into the new build, resolved in the new build but still live in the old, obsolete, too stale to judge, or in need of a human decision. Every disposition must point at source or a test that supports it, and anything undecidable is referred with the question that blocked it rather than filed away as ambiguous. Outputs one Markdown document. Trigger: the user types `/swbugs`, or says "reconcile the outstanding bugs", "which bugs migrated to Rust", "go through the open defects for both builds", "which of these are still outstanding".
swurs
Write a User Requirements Specification for a software build in Markdown — Use case / Requirement / Risk (possible) / Design input / Design output / Verification, with a source citation per requirement — and compare two builds' requirements to find what a rewrite changed, every difference classified as major / modest / minor and functional / cosmetic. Pairs the two builds on stable requirement keys rather than wording, so a reworded requirement reads as cosmetic instead of a removal plus an addition. Always previews and asks where to save. Trigger: the user types `/swurs`, or says "write a user requirements document for <software>", "what does the C# client require", "compare the C# and Rust requirements", "what changed between the two builds".
swvalidation
Turn a software build — a codebase, and optionally a test run against it — into a formal Validation document in Markdown: Number / Requirement / Contained in software / Evidence / Validation / Validation test / Validation result, one row per user-voice requirement, with every "contained in software" backed by a source citation that is fetched and checked rather than asserted. Runs in plan mode (nothing tested yet, outcome columns blank) or results mode (a test was actually run). Always previews the rows and asks where to save before writing. This is the software sibling of `/validation`, which writes .xlsx sheets for qmsWrapper modules. Trigger: the user types `/swvalidation`, or says "write a validation document for this software", "validate the C# client", "validate the Rust build", "make an .md validation for <codebase>".
swverify
Write the verification and test plan for a software build — test cases traced to URS requirement keys, oriented to the endpoints the software actually reaches — and then record what happened when the plan was executed, as a second Markdown document generated from the same spec so the plan and the record cannot drift. Computes requirement coverage, refuses a Pass with no evidence and an "observed" that merely restates the expected result, and terminates on a stated gate: PASS or HOLD, never a pass with caveats. Trigger: the user types `/swverify`, or says "write a verification plan", "make the test plan for the Rust client", "run the verification tests", "record the test results for <build>".
risk
Compile and analyse the risks for a device, a piece of software, or a system, as an ISO 14971 risk analysis: hazard, sequence of events, hazardous situation, harm, scored before and after control, with each control typed by the 14971 priority order and tied to the thing that verifies it. Works out which standards apply from what the subject actually is — ISO 13485, IEC 62304, IEC 62366-1, IEC 60601, ISO 10993, IEC 81001-5-1 and the rest — and prints the fact that pulled each one in, rather than listing standards nobody has shown to apply. Every risk level is computed from the acceptability matrix the organisation supplies; the skill refuses to invent one. Writes both a .md and a self-contained .html of the same rows, rendered from one set of computed numbers so the two cannot disagree. Trigger: the user types `/risk`, or says "analyse the risks for this", "write a risk analysis", "do the hazard analysis for the client", "which standards apply to this device", "make the 14971 file".
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.