Runs one unattended QA iteration that builds a queued test task and opens a PR on auto-qa.
npx skills add https://github.com/breaking-brake/cc-wf-studio --skill next-qa
Please help me install this Agent Skill. Skill: next-qa Source: https://github.com/breaking-brake/cc-wf-studio/tree/main/.claude/skills/next-qa Command: npx skills add https://github.com/breaking-brake/cc-wf-studio --skill next-qa
Feature branches often merge with only build and type checks as gates, so behavioral regressions slip through undetected. This Skill closes that gap by autonomously building an automated test suite, one queued QA issue per invocation, without ever touching product source code.
qa issue per run.auto-qa integration branch; product bugs are filed as bug issues with skipped regression tests instead of being fixed in place.auto-qa with main, branches, runs pnpm build && pnpm check && pnpm test, logs to docs/qa-log.md, opens a PR, and squash-merges only on green CI.auto-qa after CI passes.Ask the agent to run the next QA iteration by saying "next qa" so it stewards any open QA PR and builds one queued test issue on auto-qa.
High-intent search queries and answers about installing and using this skill.
Invoke the skill by saying "next qa" or "QAタスク". It checks for an in-flight QA PR first, then selects one queued issue labeled qa, implements the test on a branch off auto-qa, and opens a PR that squash-merges on green CI.
It picks the eligible qa issue with the best protection-to-effort ratio, preferring test infrastructure, regression tests for real bugs, then unit tests for pure logic in packages/core, cli, and mcp. Every task must protect a user-facing behavior, be deterministic, and ship in one PR.
No. The loop never edits packages/*/src. When a test surfaces a real bug, it files a bug issue and lands the test in a skipped state referencing that issue; the feature loop on auto-dev performs the actual fix.
The skill fixes the failure and re-pushes, up to three attempts. After three failed attempts it leaves the PR open, labels it needs-attention, marks the qa-log entry as blocked, and stops rather than forcing a merge.
The auto-qa integration branch is a sibling of auto-dev, both branching from main and promoted by a human. Agent merges are allowed only into auto-qa via PR with green CI, keeping autonomous test work isolated from production until human promotion.
anukkrit149Label GitHub issues and pull requests with upgrade and severity tags.
endaomentCoordinate release candidates through production deployment with human checkpoints and CI gates.
mia-cxGuide developers through red-green-refactor loops for features and bug fixes.
chanwitAutomate Red-Green-Refactor loops with unit tests and code generation.