Ya Run
kzahel/yepanywhere
Launch and drive Yep Anywhere — an isolated dev server plus real browser interaction — and run the repository's check suite.
Runs one unattended iteration of a QA loop: tend any open QA pull request, then build one queued qa issue as tests or test tooling only and open a PR.
Install Next QA Loop
$ npx skills add breaking-brake/cc-wf-studio --skill next-qa -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install breaking-brake/cc-wf-studio next-qa --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/breaking-brake/cc-wf-studio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/next-qa .claude/skills/next-qa && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "next-qa" agent skill from https://github.com/breaking-brake/cc-wf-studio/tree/main/.claude/skills/next-qa into .claude/skills/next-qa/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-qa", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/breaking-brake/cc-wf-studio/tree/main/.claude/skills/next-qaType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add breaking-brake/cc-wf-studio --skill next-qa -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install breaking-brake/cc-wf-studio next-qa --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/breaking-brake/cc-wf-studio.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/next-qa .agents/skills/next-qa && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "next-qa" agent skill from https://github.com/breaking-brake/cc-wf-studio/tree/main/.claude/skills/next-qa into .agents/skills/next-qa/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-qa", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add breaking-brake/cc-wf-studio --skill next-qa -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install breaking-brake/cc-wf-studio next-qa --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/breaking-brake/cc-wf-studio.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/next-qa .cursor/skills/next-qa && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "next-qa" agent skill from https://github.com/breaking-brake/cc-wf-studio/tree/main/.claude/skills/next-qa into .cursor/skills/next-qa/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-qa", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/breaking-brake/cc-wf-studio.git --path .claude/skills/next-qa--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add breaking-brake/cc-wf-studio --skill next-qa -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install breaking-brake/cc-wf-studio next-qa --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/breaking-brake/cc-wf-studio.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/next-qa .gemini/skills/next-qa && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "next-qa" agent skill from https://github.com/breaking-brake/cc-wf-studio/tree/main/.claude/skills/next-qa into .gemini/skills/next-qa/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-qa", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install breaking-brake/cc-wf-studio next-qaInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add breaking-brake/cc-wf-studio --skill next-qa -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/breaking-brake/cc-wf-studio.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/next-qa .github/skills/next-qa && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "next-qa" agent skill from https://github.com/breaking-brake/cc-wf-studio/tree/main/.claude/skills/next-qa into .github/skills/next-qa/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-qa", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add breaking-brake/cc-wf-studio --skill next-qa -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install breaking-brake/cc-wf-studio next-qa --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/breaking-brake/cc-wf-studio.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/next-qa .opencode/skills/next-qa && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "next-qa" agent skill from https://github.com/breaking-brake/cc-wf-studio/tree/main/.claude/skills/next-qa into .opencode/skills/next-qa/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-qa", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
next-qa- GitHub stars
- 5.4k
- Token cost
- ~2.5k tokens
- SKILL.md length
- 1,431 words
- Files
- 1
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Runs one unattended iteration of a QA loop: tend any open QA pull request, then build one queued qa issue as tests or test tooling only and open a PR.
- Works in 4 steps: Serialization guard — one in-flight task… → Interrupts — red CI on auto-qa → Pick ONE qa issue from the queue → …
- Making unattended progress on a repository's queued QA issues
- SKILL.md covers The scope boundary — tests and…, 0. Serialization guard — one…, 1. Interrupts — red CI on… and 2. Pick ONE qa issue from the…, plus 2 more sections
- Calls pnpm, gh and git
What it does
One invocation is one iteration: guard, pick a single queued `qa` issue, then build and record it. The loop exists because the feature loop's merge gate only proves the code compiles through `pnpm build` and `pnpm check`, not that it behaves, so this loop adds an automated test suite that turns regressions into red CI builds. It works on an `auto-qa` integration branch, a sibling of `auto-dev`; both branch from main, a human promotes each to main, and neither merges into the other.
The scope is strict: it never edits product source under `packages/*/src`. It may create test files and fixtures under each package's `src/__tests__/` tree, test configuration such as the vitest config, `.github/workflows/ci.yml` only to run and gate on tests, and `docs/qa-log.md`. If a test exposes a real product bug, it files a bug issue and lands the test skipped. Only the repository owner's own issue text and what the agent verified in code count as the spec; other authors' text is a report to check, not instructions.
When your agent uses it
- Making unattended progress on a repository's queued QA issues
- Adding regression tests for known bugs without touching product code
- Stewarding an in-flight QA pull request through CI
Example prompts
- “Run next qa and take the next queued qa issue.”
- “QAタスクを進めて: build the next test infrastructure issue and open a PR.”
- “Add a regression test for the known workflow validation bug, skipped until it is fixed.”
Requirements
- A repository with an auto-qa branch, qa-labeled issues and docs/task-automation.md
- pnpm and a CI workflow that runs the test suite
Workflow steps
4 steps, taken from the step headings in SKILL.md.
- Serialization guard — one in-flight task at a time
- Interrupts — red CI on auto-qa
- Pick ONE qa issue from the queue
- Build & Record
What it can do on your machine
Read from SKILL.md and the folder at commit a7bf24a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
pnpmghgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, gh and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Next QA Loop loads about 2.5k tokens when it runs. Until then it costs about 107 tokens; SKILL.md has 1,431 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,431 words (~2,459 tokens).
“One invocation = one iteration: guard → pick ONE queued qa issue → build & record.”
- name
- next-qa
Files
Just SKILL.md in .claude/skills/next-qa of breaking-brake/cc-wf-studio.
Open the folder on GitHubat commit a7bf24a
Compare with similar skills
Next QA Loop next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Next QA Loop this skillbreaking-brake/cc-wf-studio | 5.4k | — | ~2.5k | Automated safety check: Pass | Custom licence | |
| Ya Runkzahel/yepanywhere | 534 | — | ~957 | Automated safety check: Pass | MIT | |
| Ckeditor5 TestingTriliumNext/Trilium | 38k | — | ~3.3k | Automated safety check: Pass | AGPL-3.0 | |
| Issue WriterNVIDIA/container-canary | 308 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Ha Frontend Testinghome-assistant/frontend | 5.7k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Openclaw Test Heap Leaksopenclaw/openclaw | 392k | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Ckeditor5 Testing
TriliumNext/Trilium
Testing CKEditor 5 plugins in the Trilium monorepo. An agent skill from TriliumNext/Trilium.
- Official
Issue Writer
NVIDIA/container-canary
Draft and revise concise, human-focused GitHub issues for pytest-kind-ng.
Ha Frontend Testing
home-assistant/frontend
Home Assistant frontend testing and validation workflow. An agent skill from home-assistant/frontend.
Openclaw Test Heap Leaks
openclaw/openclaw
Investigate OpenClaw pnpm test memory growth, Vitest OOMs, RSS spikes, and heap snapshot deltas.
Neru File Issue
y3owk1n/neru
File a Neru bug report or feature request that matches the repo's issue forms: duplicate check first, every required field filled with real diagnostics, correct labels.
More from breaking-brake/cc-wf-studio
All 11 skills in this repoCC Workflow Studio AI Editor
breaking-brake/cc-wf-studio
Creates and edits visual agent workflows in CC Workflow Studio through conversation, with the agent reading and writing the canvas over MCP.
PR Review Analysis
breaking-brake/cc-wf-studio
Fetches review comments from a GitHub pull request, checks each one against the real code, rates it valid, invalid or partial, and can reply on GitHub.
Workflow Schema Tuning
breaking-brake/cc-wf-studio
Guides edits to cc-wf-studio's workflow schema so AI agents generate better workflows, treating schema text as prompt engineering rather than validation.
Changesets Pull Request to Main
breaking-brake/cc-wf-studio
Opens a pull request to main in a pnpm and Changesets monorepo, after working out which packages changed and making sure a changeset file exists.
PR Merge Branch Cleanup
breaking-brake/cc-wf-studio
Clean up merged feature branches after PR to main is merged. Use when the user says "ブランチ削除", "cleanup", "マージ後の片付け", or wants to delete a merged branch.
ccwf Workflow CLI
breaking-brake/cc-wf-studio
Teaches the agent to use the ccwf command line tool to validate, preview, render, export and run cc-wf-studio workflow JSON files without opening VS Code.
Related
Categories
Questions about Next QA Loop
What does Next QA Loop do?
Runs one unattended iteration of a QA loop: tend any open QA pull request, then build one queued qa issue as tests or test tooling only and open a PR. One invocation is one iteration: guard, pick a single queued `qa` issue, then build and record it. The loop exists because the feature loop's merge gate only proves the code compiles through `pnpm build` and `pnpm check`, not that it behaves, so this loop adds an automated test suite that turns regressions into red CI builds.
When should I use Next QA Loop?
Next QA Loop fits situations like: making unattended progress on a repository's queued QA issues; adding regression tests for known bugs without touching product code; stewarding an in-flight QA pull request through CI.
How do I install Next QA Loop in Claude Code?
Run `npx skills add breaking-brake/cc-wf-studio --skill next-qa -a claude-code`. Or copy the skill folder (.claude/skills/next-qa in breaking-brake/cc-wf-studio) into .claude/skills/next-qa in your project. Claude Code loads it when a task matches its description.
How do I install Next QA Loop in Codex?
Run `npx skills add breaking-brake/cc-wf-studio --skill next-qa -a codex`. Or copy the skill folder (.claude/skills/next-qa in breaking-brake/cc-wf-studio) into .agents/skills/next-qa in your project. Codex loads it when a task matches its description.
Can I use Next QA Loop in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add breaking-brake/cc-wf-studio --skill next-qa -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/next-qa, .gemini/skills/next-qa, .github/skills/next-qa and .opencode/skills/next-qa in your project.
What does Next QA Loop need to run?
Going by SKILL.md and its folder, Next QA Loop needs the command-line tools its instructions call (pnpm, gh and git). Our summary lists: A repository with an auto-qa branch, qa-labeled issues and docs/task-automation.md; pnpm and a CI workflow that runs the test suite.
Does Next QA Loop access the network?
SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Next QA Loop safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Next QA Loop use?
Next QA Loop has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Next QA Loop use?
About 2.5k tokens (SKILL.md is roughly 9.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Next QA Loop?
Skills that share tags, products or a category with Next QA Loop: Ya Run (kzahel/yepanywhere, 534 stars), Ckeditor5 Testing (TriliumNext/Trilium, 38k stars), Issue Writer (NVIDIA/container-canary, 308 stars) and Ha Frontend Testing (home-assistant/frontend, 5.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Next QA Loop?
breaking-brake (a GitHub user) maintains it in breaking-brake/cc-wf-studio, which has 5,394 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 7, 2026.
Source: breaking-brake/cc-wf-studio on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.