team-qa
Skill69 starsChanged 19 days agoMITView on GitHub
Test strategy and quality assurance methodology. Acceptance criterion -> test conversion, edge cases, e2e coverage. The playbook of the qa role.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- chuanglibs/Claude-Code-Game-Studios-Codextheir own version, first seen Nov 15, 2026
- Donchitos/Claude-Code-Game-Studiostheir own version, first seen Nov 9, 2026
- striderZA/OpenCodeGameStudiostheir own version, first seen Nov 4, 2026
- venus2099/codex-game-studiostheir own version, first seen Oct 17, 2026
- HunLuanZhiZhu/Game-Studios-Plugintheir own version, first seen Oct 5, 2026
- dawn840705/claude-code-studiostheir own version, first seen Aug 28, 2026
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- striderZA/OpenCodeGameStudios★ 124same name
- cenconq25/claude-code-app-studio★ 40same name
- DangQuangSE/team-development-skills★ 19same name
- dawn840705/codex-code-studios★ 17same name
- lilangMax/ClaudeCodeGameStudios★ 8same name
- hongyuanc/codex-game-studios★ 5same name
- chuanglibs/Claude-Code-Game-Studios-Codex★ 1same name
- dawn840705/claude-code-studios★ 1same name
- HunLuanZhiZhu/Game-Studios-Plugin★ 1same name
1 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- docs/agents.mdAGENTS.md
- team/AGENTS.mdAGENTS.md
- team-architectureSkill
- team-backlogSkill
- team-brandSkill
- team-buildSkill
- team-disciplineSkill
- team-docsSkill
- team-marketingSkill
- team-market-researchSkill
- team-memorySkill
- team-prdSkill
- team-releaseSkill
- team-security-reviewSkill
- team-uxSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Every acceptance criterion in the backlog must have a test.
- Distinctive: line 22
If there is no test that meets a criterion, that criterion is untested.
- Distinctive: line 32
Do not write e2e for everything.
- Distinctive: line 67
Do not write tests that look inside the application and verify it (if what is mocked does not represent reality, the test is useless)
- Distinctive: line 69
If it depends on time or randomness, fix it
- Distinctive: line 77
Do not fix a finding before writing the test.
- Distinctive: line 92
Do not show a criterion you could not test as "passed".
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Quality Assurance
What a test is
A test is the verification of an acceptance criterion. Not a test that shows the code runs, but a test that shows the behavior is correct.
The purpose of writing tests is code reliability, not coverage percentage.
1. Acceptance criterion -> test
Every acceptance criterion in the backlog must have a test. Build a mapping table:
| Criterion | Test | Type | Status |
| "No invoices" is shown on an empty list | renders_empty_state_when_no_invoices | unit | ✅ |
If there is no test that meets a criterion, that criterion is untested. Not "passed".
2. The test pyramid
| Type | What it tests | Ratio | Speed |
| Unit | Business logic, edge cases | 70% | ms |
| Integration | DB, API, file system | 20% | s |
| e2e | The user journey | 10% | s-min |
Do not write e2e for everything. e2e is fragile and slow; use it only for the main journeys that bring in money.
3. Mandatory edge cases
For every endpoint and every form:
| Case | Expected |
| Empty input | 400 + a meaningful error, not 500 |
| Oversized input | 413 or a controlled error |
| Corrupt data (invalid JSON, broken encoding) | 400, no crash |
| Unauthorized access | 403 + no resource leakage |
| Resource not found | 404, without leaking another user's data |
| The same request twice | No effect (idempotent, or no duplicate record) |
| Two concurrent requests | No data corruption (race condition) |
| Database connection dropped | Not 5xx, a proper error body |
4. Test quality
Bad test — does not verify the application:
def test_invoice():
assert invoice is not NoneGood test — verifies the behavior:
def test_parse_invoice_returns_none_for_missing_total():
result = parse_invoice("Invoice No: 123\nDate: 2026-01-01")
assert result["total"] is NoneRules:
- The test name should tell the behavior
- Each test verifies one behavior
- Do not write tests that look inside the application and verify it (if what is mocked does not represent reality, the test is useless)
- Tests should be independent of each other, order should not matter
- If it depends on time or randomness, fix it
5. Finding-fix loop
Finding -> Write the test (FIRST) -> See the test fail -> Fix the code -> Test passes -> RefactorDo not fix a finding before writing the test. If the test is written afterwards, it does not verify the fix.
6. The trap of weakening a test
Deleting or loosening an assertion to make a test pass is not a fix. Do not do any of these:
assert x == 5→assert x is not None- Adding
pytest.skip/test.skip - Commenting out a line
- Increasing the timeout (it hides race conditions)
7. Reporting
| Criterion | Test | Result |
Do not show a criterion you could not test as "passed". Write "not testable + rationale".
Output format
Markdown: Scope mapping table / Actual test run output / Bugs found and fixed / Not tested + rationale / Remaining risks.
In the user's language (Turkish or English).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

