Generate spec-traced quality engineering audits with test and review artifacts.
npx skills add https://github.com/selfagency/agentsy --skill quality-playbook
Please help me install this Agent Skill. Skill: quality-playbook Source: https://github.com/selfagency/agentsy/tree/main/.agents/skills/quality-playbook Command: npx skills add https://github.com/selfagency/agentsy --skill quality-playbook
It solves the problem of inconsistent and incomplete quality assurance by converting a codebase into a durable, spec-traced quality system. Instead of only running tests or performing superficial reviews, it discovers requirements from the code and available documentation, then validates those requirements via a structured audit pipeline with explicit traceability.
Typical use cases include self-auditing a project’s readiness for release, generating a quality system for a new repository, or performing repeatable quality engineering across languages and frameworks.
Run the quality-playbook on your target repository by telling an AI agent: "Run the Quality Playbook" (optionally with a hint like "self-audit" or "quality playbook").
High-intent search queries and answers about installing and using this skill.
To generate testable requirements from an existing codebase, you can run a spec audit that discovers behavioral requirements from code and documentation, producing an auditable quality constitution with explicit traceability.
A spec-traced quality engineering audit is a process that derives behavioral requirements from a repository and validates them through a structured pipeline, producing traceable test and code review artifacts.
You can verify bug fixes using TDD red-green testing by running a structured audit loop that confirms defects, applies regression-tested patches, and produces a consolidated bug report.
Yes, you can perform a multi-pass code review across cross-language repositories by applying a three-pass structural review combined with a multi-model spec audit to find defects missed by standard reviews.
The best way to reconcile test coverage for repeated quality audits is to run a spec-traced pipeline that maps behavioral requirements to tests, ensuring durable coverage reconciliation across re-runs.
No, you do not need automated testing already set up to derive a quality system, as the process discovers requirements from code and documentation before validating them through TDD red-green verification.
sperictaoBootstrap Trellis specs from repository architecture analysis and documentation.
moongci38-ossAutomate bug fixing via TDD red-green cycle and update report status.
heyallencaoRun automated test suites and coverage checks to validate code claims.
Negentropy-LabyValidate skill definitions across static, spec, category, and audit modes.
