{"id":77008,"plugin_id":"plugins_6ab41ed5b8c4819199eb5bbf91ce25f5","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:12:18.678Z","digest":"5464616cdffb5f2cd823c92393f13b1b28545abbee95064341070fed7be28b87","against":null,"payload":{"description":"Create targeted unit, integration, contract, regression and end-to-end verification for an existing code change or defect.","included_files":[],"name":"design-and-run-tests","skill_md_contents":"---\nname: design-and-run-tests\ndescription: Create targeted unit, integration, contract, regression and end-to-end verification for an existing code change or defect.\n---\n\n# Design And Run Tests\n\nUse this skill only for its stated purpose. Follow the shared source-of-truth, permission and evidence rules in `../../references/workflow-contract.md`. Read `../../references/testing-and-evidence.md` for detailed method when necessary.\n\n## Procedure\n1. Identify user-visible behavior and failure boundaries of the change.\n2. Select the smallest tests that establish correctness; include realistic negative/edge cases.\n3. Write reusable fixtures and tests that fail for a meaningful regression.\n4. Execute tests when runtime tools are present; record commands and actual results.\n5. Flag missing execution tools or untested boundaries without inventing a green suite.\nUse `../../templates/test-matrix.md` for complex changes.\n\n## Handoff rule\nState actual artifacts or grounded code findings and validation status. Never invent file paths, executed tests, tool access, or completed subagent work. Keep output proportionate to the user request.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}