Orchestrate build, test, security, wiring, and spec compliance quality gates.
npx skills add https://github.com/Obsidian-Owl/specwright --skill sw-verify
Please help me install this Agent Skill. Skill: sw-verify Source: https://github.com/Obsidian-Owl/specwright/tree/main/skills/sw-verify Command: npx skills add https://github.com/Obsidian-Owl/specwright --skill sw-verify
This Skill ensures that code meets quality standards and fulfills its intended purpose by running a series of automated checks, preventing the shipment of faulty or incomplete features.
sw-verify to catch any build errors, failing tests, security vulnerabilities, or deviations from the original specification, ensuring a robust and reliable release.Run the sw-verify skill to execute all enabled quality gates for the current work unit.
High-intent search queries and answers about installing and using this skill.
A quality gate orchestrator verifies code correctness by executing predefined checks like build, tests, security, and spec compliance in a specific order. It manages gate execution, handles failures interactively, and produces an evidence report for review before shipping.
A quality gate in CI/CD is an automated checkpoint that validates code against defined acceptance criteria to ensure spec compliance. It checks build integrity, security vulnerabilities, and test failures, presenting issues interactively with recommended actions before code is shipped.
You can run security and wiring checks against defined acceptance criteria by orchestrating them as sequential quality gates. This automated verification detects vulnerabilities and integration issues, mapping the results to an aggregate evidence report for user review.
Yes, you can handle test failures interactively during code review by orchestrating quality gates that pause upon detecting issues. The system presents all detected errors with clear explanations and recommended actions, allowing you to resolve problems before proceeding.
The best way to generate an aggregate evidence report for code review is to run automated verification checks that map acceptance criteria directly to code and test evidence. This ensures all build, security, and spec compliance results are documented before shipping.
You should avoid relying solely on automated quality gates for verification when your project lacks defined acceptance criteria or a stable build environment. Without clear specifications to map against, the evidence report cannot effectively validate correctness or prevent faulty releases.
chenluhanDefine measurable acceptance criteria and success metrics for feature handoffs.
VirtoCommerceValidate merged commits and release verified fixes as controlled hotfix patches.
winsorllcExecute linters, static analysis, and security scanners on code.
DarkMonkDevRun unit, integration, and end-to-end tests in isolated containers.