Run a multi-phase QA pipeline on changed files after build.
npx skills add https://github.com/davekim917/bootstrap --skill team-qa-davekim917
Please help me install this Agent Skill. Skill: team-qa Source: https://github.com/davekim917/bootstrap/tree/main/plugins/workflow/skills/team-qa Command: npx skills add https://github.com/davekim917/bootstrap --skill team-qa-davekim917
After a team build, QA often hinges on manual checks and scattered validation steps. This skill automates post-build quality validation by running a structured, multi-phase pipeline on changed files.
Trigger this skill after a successful /team-build to run the automated QA pipeline on the latest changes.
High-intent search queries and answers about installing and using this skill.
Automated post-build code quality validation runs a multi-phase QA pipeline on changed files, applying sequential denoise and parallel validators to generate a structured QA report. It enforces MUST-FIX gating before shipping to ensure codebase standards are met.
A Codex adversarial pass is a parallel validation step within a QA pipeline that stress-tests changed files for edge cases and vulnerabilities. It runs alongside style, docs freshness, and domain-specific code review swarm validators to isolate and surface critical findings.
Running a parallel code review swarm and validators requires triggering an automated post-build QA pipeline after a successful team-build completes. The pipeline orchestrates isolated validators for style, docs, and code review with selective re-run logic to minimize blast radius.
Yes, automated QA requires a completed build and CLAUDE.md conventions to execute the post-build validation pipeline properly. These prerequisites ensure the multi-phase validators have the necessary context and artifacts to enforce MUST-FIX gating before shipping.
Gating shipping based on MUST-FIX findings is handled natively by the automated QA pipeline, which consolidates validator outputs into a structured report. It enforces the gate automatically, preventing deployment until critical findings are resolved and selective re-runs pass.
Validator isolation in post-build QA pipelines minimizes blast radius and feedback cycles by containing failures to specific checks like style or docs freshness. This allows selective re-runs of failed validators without re-executing the entire multi-phase pipeline.
ZeliperSpawn commit-agent to create TASK-ID-scoped commits after successful builds.
nselugaApply optimization and QA findings to fix code issues.
acarmonagCoordinate a multi-agent swarm to review GitHub pull requests for security, performance, architecture, and style issues.
vrcmsExecute build, type, lint, test, and security checks in a verification pipeline.
