Generate spec-driven tests from documentation, designs, and contracts.
npx skills add https://github.com/nklisch/skills --skill test-quality-nklisch
Please help me install this Agent Skill. Skill: test-quality Source: https://github.com/nklisch/skills/tree/main/plugins/workflow/skills/test-quality Command: npx skills add https://github.com/nklisch/skills --skill test-quality-nklisch
Many projects rely on tests written from existing implementation code, which leads to tautological testing that fails to catch real bugs. This Skill addresses the lack of spec‑driven test coverage, helping teams discover gaps, edge cases, and contract violations.
Run the test-quality skill on a target module to generate missing spec‑driven tests.
High-intent search queries and answers about installing and using this skill.
To generate spec-driven tests, the skill scans documentation, design files, and interface definitions to extract behavioral contracts. It then creates new test cases referencing these specifications, prioritizing invalid inputs, boundary values, and error paths to avoid tautological testing.
Your test suite likely fails because tests were written from existing implementation code, leading to tautological testing. Spec-driven test generation solves this by deriving tests from behavioral specifications and design contracts, actively uncovering coverage gaps and edge cases.
The best way to find coverage gaps is through contract discovery and gap analysis. The skill compares your existing test suites against extracted behavioral specifications from documentation to systematically identify untested scenarios and contract violations.
Yes, you can analyze interface definitions to generate tests for edge cases. The skill locates contracts using glob and grep tools, then applies spec-driven test generation to prioritize boundary values, invalid inputs, and error paths.
No, you do not need existing test suites. The skill is designed for codebases where behavior is described in documentation, applying contract discovery to generate new tests and analyze coverage gaps independently of existing tests.
Yes, spec-driven test generation works with documentation files. It leverages task tools to orchestrate the testing workflow, creating subtasks and tracking progress to ensure systematic coverage of extracted behavioral specifications.
jMertaGenerate a comprehensive CLI specification covering commands, arguments, flags, and UX.
forcedotcomExecute Salesforce Apex unit tests with coverage analysis and failure diagnosis.
AndyHsuTWAutomate Django project verification with linters, security scanners, and tests.
jonnymuirAudit C# security regression suites to separate genuine vulnerabilities from placeholder tests.
