Not in the top 1,000 by GitHub stars
QAMarcos/claude-qa-flow
QA workflow for AI coding agents: ticket → reviewed test plan → real-browser run with independent evidence review → bug tickets. Claude Code, OpenCode, any Agent Skills harness.
History
Review weekly changes to SKILL.md before updating. Dates mark the weeks in which we observed each version; checks apply to the recorded commits.
View weekly changes
skills/create-test-plan-scenarios/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
f7f1441e5c86 → f7f1441e5c86
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → f7f1441e5c86
No earlier version was observed for comparison.
skills/file-bug-ticket/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
f7f1441e5c86 → f7f1441e5c86
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → f7f1441e5c86
No earlier version was observed for comparison.
skills/manual-test/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
f7f1441e5c86 → f7f1441e5c86
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → f7f1441e5c86
No earlier version was observed for comparison.
Verified commit f7f1441e5c86ff289afb7189a16e4cff52769279
git clone --filter=blob:none --no-checkout https://github.com/QAMarcos/claude-qa-flow.git .hotskills/qamarcos-claude-qa-flow && git -C .hotskills/qamarcos-claude-qa-flow checkout --detach f7f1441e5c86ff289afb7189a16e4cff52769279
# Copy each selected skill directory from .hotskills/qamarcos-claude-qa-flow into .claude/skills/<skill-name>/Heat
1.6- Star growth, last 7 daysNot available
- Star growth, last 24 hoursNot available
- Rank movement, last 7 daysNot available
- Commits, last 30 daysNot available
- Accounts asking about it through MCP, last 7 daysNot available
- Hot votes this weekNot available
Heat never changes the order by stars, and sponsorship never touches it. How heat works
Stars over time
30-day change not yet available: not enough history.
Individual skills in this repository
- create-test-plan-scenarios
skills/create-test-plan-scenarios - file-bug-ticket
skills/file-bug-ticket - manual-test
skills/manual-test
How it works
create-test-plan-scenarios
When your agent uses it
Turn a task/ticket into a structured, professional QA test plan — a checklist of atomic, executable scenarios — and (optionally) post it back to your issue tracker. Use whenever the user asks to "create a test plan", "list test scenarios", "criar cenários de teste", "QA checklist for TICKET-XXXX", or otherwise wants a ticket turned into a verifiable QA plan. Works for any story type (UI, API, mobile, infra). Always runs a self-review pass before writing anything back.
What it loads into context
Frontmatter
178 tokensAlways available to the agent
SKILL.md
2,316 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Step 0 — Triage & delegation (mandatory)
- Configuration (fill these in for your setup)
- Inputs
- Workflow
- Errors
- Notes
Files
../../.claude-plugin/marketplace.jsonasset613 bytes../../.claude-plugin/plugin.jsonasset515 bytes../../hooks/hooks.jsonasset301 bytes../../hooks/hooks.jsonasset301 bytesSKILL.mdcore9,952 bytesSKILL.mdcore9,952 bytesSKILL.mdcore9,952 bytesSKILL.mdcore9,952 bytesSKILL.mdcore9,952 bytes
Read SKILL.md
# Create Test Plan Scenarios
Turns any task/ticket into a structured, professional QA test plan: a checklist of atomic, observable, independently-runnable scenarios. Optionally posts the checklist back to your issue tracker as native sub-tasks. Works for UI, API, mobile, and infra stories. Always runs a self-review pass before writing anything.
> These scenarios are the source of truth consumed by the `manual-test` skill, which executes them against the running app. Keep each one atomic and observable so it maps cleanly to an executable step.
## Step 0 — Triage & delegation (mandatory)
This skill is a **router**: generation and self-review go to a subagent; the posting gate stays with
the user in the main conversation.
**Delegated (subagent, fresh context):** read the ticket, draft the checklist, and run the
self-review — Steps 1–5. The subagent **returns the checklist; it does not post.** Suggested brief:
View the complete source on GitHubfile-bug-ticket
When your agent uses it
File a bug (or feature/chore) ticket in your issue tracker via its REST API with a terse, budgeted description, attached screenshot evidence, owner/priority/placement filled in, and a verification GET before reporting done. Use whenever the user asks to "file a bug", "open a ticket", "criar um card", "abrir um bug", "report this to the tracker", or when manual-test hands over findings to file. Tracker-agnostic (Jira, Linear, GitHub Issues, Shortcut, ...).
What it loads into context
Frontmatter
176 tokensAlways available to the agent
SKILL.md
2,093 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Step 0 — Triage & delegation (mandatory)
- Configuration (fill these in for your setup)
- Default field choices
- Owner, priority and placement — always filled
- Description template — default: terse
- Workflow
- Errors
Files
SKILL.mdcore8,763 bytesSKILL.mdcore8,763 bytesSKILL.mdcore8,763 bytes
Read SKILL.md
# File Bug Ticket
Creates a ticket in your issue tracker through its REST API: terse English description inside a
character budget, screenshots attached, owner / priority / placement always filled, and the result
verified before it is reported. Default type is a bug, but features and chores work the same way.
> Called directly by the user, or by `manual-test` (Step 7) with fields and body already resolved.
## Step 0 — Triage & delegation (mandatory)
This skill is a **router**. Creating a ticket is an external write — never delegate with a field
left to guess.
**Stays inline (main conversation):** resolve what is ambiguous — title, type, state, epic/project,View the complete source on GitHubmanual-test
When your agent uses it
Execute exploratory/manual QA against a web app, driven by either a ticket's test plan or a single ad-hoc scenario the user describes. Use whenever the user asks to "run a manual test", "fazer um teste manual", "execute this scenario", "validate this ticket manually", "manual test for TICKET-XXXX", or otherwise wants the agent to step through a behavior in the real app and report pass/fail with evidence. Resolves context with the user, delegates execution to an executor subagent, has the evidence checked by an independent reviewer, and only then (with approval) writes back to the tracker.
What it loads into context
Frontmatter
203 tokensAlways available to the agent
SKILL.md
4,538 tokensWhen the skill is activated
Reference documents
5,900 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Model tiers used below
- Step 0 — Triage & delegation (mandatory)
- Two modes
- Configuration (fill these in for your setup)
- Auth & secrets
- Workflow
- Rules
- Errors
- Notes
Files
SKILL.mdcore19,248 bytesSKILL.mdcore19,248 bytesreferences/evidence-discipline.mddoc2,447 bytesreferences/filing-and-comments.mddoc4,876 bytesreferences/playwright-templates.mddoc4,633 bytesreferences/report-format.mddoc2,403 bytesreferences/severity-gate.mddoc3,025 bytesroles/evidence-reviewer.mddoc3,458 bytesroles/test-executor.mddoc3,740 bytes
Read SKILL.md
# Manual Test
Drives manual / exploratory QA against a web app. Reads the test context (from an issue-tracker
ticket or directly from the user), executes it by piloting a real browser through a throwaway
Playwright script, has the evidence independently reviewed, and reports pass/fail. **Does not commit
any test files** — every script written here is throwaway and lives in a git-ignored scratch root.
> Pairs with `create-test-plan-scenarios` (produces the checklist) and `file-bug-ticket` (files the
> bugs this run finds).
## Model tiers used below
Tiers are capability levels, not vendor names — map them to what your harness offers:
View the complete source on GitHubSkills included
- create-test-plan-scenarios
- file-bug-ticket
- manual-test
Repository facts
- License
- MIT
- Created
- Jul 3, 2026
- Last pushed
- Nov 3, 2026
- Forks
- 0
- Open issues
- 0
- Project activity
- Active
Before you install
Network or broad shellAutomated signals, not a guarantee
Checked Nov 6, 2026
Not fully analyzed: some files were too long, unreadable or missing. This never lowers the level.
Show 8 notes
hooks/hooks.json:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/create-test-plan-scenarios/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/create-test-plan-scenarios/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/create-test-plan-scenarios/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/create-test-plan-scenarios/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/file-bug-ticket/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/file-bug-ticket/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/manual-test/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed
- No broad tool permissions
- No dangerous shell commands
- 22 network referencesin 4 files: create-test-plan-scenarios/SKILL.md:3 manual-test/references/playwright-templates.md:23 .claude-plugin/plugin.json:4 and 1 more
- No hidden or obfuscated text
- No instruction overrides
- No executable scripts
- 7 references to secretsin 3 files: create-test-plan-scenarios/SKILL.md:78 file-bug-ticket/SKILL.md:151 manual-test/references/playwright-templates.md:46
- No requests to vote in Hot
Show all 29 signals by file
.claude-plugin/plugin.json
- Network accessline 4
"description": "Ticket → reviewed QA test plan → real-browser execution with evidence → independent review → terse bug tickets. Tracker-agnostic, Playwright-driven.", "author": { "name": "Marcos Pereira" }, "homepage": "https://github.c - Network accessline 5
"author": { "name": "Marcos Pereira" }, "homepage": "https://github.com/QAMarcos/claude-qa-flow", "repository": "https://github.com/QAMarcos/claude-qa-flow", - Network accessline 6
"homepage": "https://github.com/QAMarcos/claude-qa-flow", - Network accessline 7
"repository": "https://github.com/QAMarcos/claude-qa-flow",
skills/create-test-plan-scenarios/SKILL.md
- Network accessline 3
description: Turn a task/ticket into a structured, professional QA test plan — a checklist of atomic, executable scenarios — and (optionally) post it back to your issue tracker. Use whenever the user asks to "create a test plan", "list test - Network accessline 4
license: MIT compatibility: Any Agent Skills harness (Claude Code, OpenCode, Codex, ...). Tracker write-back needs shell access with curl (or equivalent) and an API token. Subagents recommended. metadata: - Network accessline 5
compatibility: Any Agent Skills harness (Claude Code, OpenCode, Codex, ...). Tracker write-back needs shell access with curl (or equivalent) and an API token. Subagents recommended. - Network accessline 54
- **`TRACKER_API_BASE`** — base URL of your tracker's REST API (e.g. `https://your-tracker.example.com/api/v3`). - Network accessline 56
- **`TRACKER_STORY_URL`** — the human-facing URL pattern for a ticket (e.g. `https://your-tracker.example.com/story/<ID>`). - Network accessline 63
- a bare id: `1234` - a prefixed id: `TICKET-1234` - a full URL: `https://your-tracker.example.com/story/1234/anything-after` - Network accessline 65
- a full URL: `https://your-tracker.example.com/story/1234/anything-after` - Network accessline 78
[Credential-related source omitted] - Access to secretsline 78
[Credential-related source omitted] - Network accessline 141
[Credential-related source omitted] - Access to secretsline 141
[Credential-related source omitted] - Access to secretsline 142
[Credential-related source omitted]
skills/file-bug-ticket/SKILL.md
- Network accessline 3
description: File a bug (or feature/chore) ticket in your issue tracker via its REST API with a terse, budgeted description, attached screenshot evidence, owner/priority/placement filled in, and a verification GET before reporting done. Use - Network accessline 4
license: MIT compatibility: Any Agent Skills harness (Claude Code, OpenCode, Codex, ...). Needs shell access with curl (or equivalent) and a tracker API token. Subagents optional. metadata: - Network accessline 5
compatibility: Any Agent Skills harness (Claude Code, OpenCode, Codex, ...). Needs shell access with curl (or equivalent) and a tracker API token. Subagents optional. - Network accessline 151
[Credential-related source omitted] - Access to secretsline 151
[Credential-related source omitted] - Access to secretsline 152
[Credential-related source omitted]
skills/manual-test/references/playwright-templates.md
- Network accessline 23
test("manual: <one-line description>", async ({ page }) => { await page.goto("https://staging.<your-app>.example.com/<entry-point>"); - Network accessline 24
await page.goto("https://staging.<your-app>.example.com/<entry-point>"); - Access to secretsline 46
[Credential-related source omitted] - Access to secretsline 65
[Credential-related source omitted] - Network accessline 90
const NOISE = /(analytics|googletagmanager|google-analytics|sentry|fonts\.|\.(png|jpe?g|svg|woff2?|css|js)(\?|$))/i; const requests: string[] = []; page.on("request", r => { if (!NOISE.test(r.url())) requests.push(`${r.method()} ${r.url()}` - Network accessline 91
const requests: string[] = []; page.on("request", r => { if (!NOISE.test(r.url())) requests.push(`${r.method()} ${r.url()}`); }); page.on("response", async r => { if (!NOISE.test(r.url())) console.log(` <- ${r.status()} ${r.url()}`); }); - Network accessline 92
page.on("request", r => { if (!NOISE.test(r.url())) requests.push(`${r.method()} ${r.url()}`); });
How the signals fit together
Facts from a static read of the files at the pinned commit. They describe what the code does, not why.
Some files could not be read; the facts below still hold.
Signal confidence: 25 facts
- Network access in the frontmatter of the SKILL.mdcreate-test-plan-scenarios/SKILL.md:3Low confidence
- Network access in the frontmatter of the SKILL.mdcreate-test-plan-scenarios/SKILL.md:4Low confidence
- Network access in the frontmatter of the SKILL.mdcreate-test-plan-scenarios/SKILL.md:5Low confidence
- Network access in prose of the SKILL.mdcreate-test-plan-scenarios/SKILL.md:54Low confidence
- Network access in prose of the SKILL.mdcreate-test-plan-scenarios/SKILL.md:56Low confidence
- Network access in prose of the SKILL.mdcreate-test-plan-scenarios/SKILL.md:63Low confidence
- Network access in prose of the SKILL.mdcreate-test-plan-scenarios/SKILL.md:65Low confidence
- Network access in code of the SKILL.mdcreate-test-plan-scenarios/SKILL.md:78High confidence
- Access to secrets in code of the SKILL.md: a variable, placeholder or call, not a stored valuecreate-test-plan-scenarios/SKILL.md:78Low confidence
- Network access in code of the SKILL.mdcreate-test-plan-scenarios/SKILL.md:141High confidence
- Access to secrets in code of the SKILL.mdcreate-test-plan-scenarios/SKILL.md:141High confidence
- Access to secrets in code of the SKILL.md: a variable, placeholder or call, not a stored valuecreate-test-plan-scenarios/SKILL.md:142Low confidence
- Network access in the frontmatter of the SKILL.mdfile-bug-ticket/SKILL.md:3Low confidence
- Network access in the frontmatter of the SKILL.mdfile-bug-ticket/SKILL.md:4Low confidence
- Network access in the frontmatter of the SKILL.mdfile-bug-ticket/SKILL.md:5Low confidence
- Network access in code of the SKILL.mdfile-bug-ticket/SKILL.md:151High confidence
- Access to secrets in code of the SKILL.mdfile-bug-ticket/SKILL.md:151High confidence
- Access to secrets in code of the SKILL.md: a variable, placeholder or call, not a stored valuefile-bug-ticket/SKILL.md:152Low confidence
- Network access in code of documentationmanual-test/references/playwright-templates.md:23Low confidence
- Network access in code of documentationmanual-test/references/playwright-templates.md:24Low confidence
- Access to secrets in code of documentation: a variable, placeholder or call, not a stored valuemanual-test/references/playwright-templates.md:46Low confidence
- Access to secrets in code of documentation: a variable, placeholder or call, not a stored valuemanual-test/references/playwright-templates.md:65Low confidence
- Network access in code of documentationmanual-test/references/playwright-templates.md:90Low confidence
- Network access in code of documentationmanual-test/references/playwright-templates.md:91Low confidence
- Network access in code of documentationmanual-test/references/playwright-templates.md:92Low confidence
Works with
| Agent | Status | Evidence | Install to |
|---|---|---|---|
| Claude Code | Native | Manifest .claude-plugin/marketplace.json | .claude/skills/<skill-name>/ |
| Codex | Compatible | Standard SKILL.md skills/create-test-plan-scenarios/SKILL.md | .agents/skills/<skill-name>/ |
| Cursor | Compatible | Standard SKILL.md skills/create-test-plan-scenarios/SKILL.md | .cursor/skills/<skill-name>/ |
| Gemini CLI | Compatible | Standard SKILL.md skills/create-test-plan-scenarios/SKILL.md | .gemini/skills/<skill-name>/ |
| GitHub Copilot | Compatible | Standard SKILL.md skills/create-test-plan-scenarios/SKILL.md | .github/skills/<skill-name>/ |
| OpenCode | Compatible | Standard SKILL.md skills/create-test-plan-scenarios/SKILL.md | .opencode/skills/<skill-name>/ |
- Native The repository ships a manifest, folder or frontmatter field for this agent.
- Compatible A standard SKILL.md that this agent can read.
- Unknown No evidence either way.
Derived automatically from paths, manifests and frontmatter. Not tested on each agent.