Skip to main content
skill CX Codex

team-qa · sametcelikbicak — Claude Code skill: testing and installation

team-qa is a Claude Code skill that turns acceptance criteria into tests and sets out a QA approach. It covers edge cases, key user journeys, and bug fixes.

MIT ★ 71 updated 2026-11-13

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add sametcelikbicak/opencode-team --skill team-qa -a claude-code
Open on GitHub

What team-qa does

team-qa maps each acceptance criterion to a test and its result. It separates checks into unit, integration, and e2e tests, and calls for endpoint and form cases such as empty or oversized input, access failures, duplicate requests, and database connection loss.

For a reported bug, write a test before changing the code. Weakening an assertion or skipping the test does not count as a fix. The Markdown report includes the criterion-to-test mapping, actual run output, fixed bugs, untested items with reasons, and remaining risks. E2e tests are reserved for core user journeys because they are slow and fragile.

What it helps with

  • map acceptance criteria to tests
  • check how endpoints handle invalid input
  • cover important user journeys with e2e tests
  • report test results and remaining risks

Example prompts for the agent

  • Create a test plan for these acceptance criteria and map each one to a check.
  • Check this endpoint for edge cases, including repeated and concurrent requests.
  • Investigate this bug by adding a test first, then fixing the code and writing the report.

How to install team-qa

1Skills CLI (Vercel)

npx skills add sametcelikbicak/opencode-team --skill team-qa -a claude-code

2Manually: put the files in place

~/.claude/skills/team-qa/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/team-qa/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about team-qa

How do I install team-qa in Claude Code?

Run npx skills add sametcelikbicak/opencode-team --skill team-qa -a claude-code. The skill file is at ~/.claude/skills/team-qa/SKILL.md.

What does team-qa do?

It helps turn acceptance criteria into tests, choose test types, and cover edge cases. Its bug-fix workflow puts the test before the code change.

Which edge cases does team-qa cover for endpoints and forms?

It includes empty or oversized input, corrupt data, unauthorized access, repeated and concurrent requests, and dropped database connections.

Source text

SKILL.md · MIT
---
name: team-qa
description: Test strategy and quality assurance methodology. Acceptance criterion -> test conversion, edge cases, e2e coverage. The playbook of the qa role.
---

# 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:
```python
def test_invoice():
    assert invoice is not None
```

**Good test** — verifies the behavior:
```python
def test_parse_invoice_returns_none_for_missing_total():
    result = parse_invoice("Invoice No: 123\nDate: 2026-01-01")
    assert result["total"] is None
```

Rules:
- 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 -> Refactor
```

Do 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).

© sametcelikbicak · MIT · sametcelikbicak/opencode-team

Similar skills

All skills for Testing and QA →

team-qa by other authors comes first.

team-qa Donchitos team-qa orchestrates a full QA cycle: qa-lead builds strategy and test plan, qa-tester writes test cases, executes checks, and produces sign-off reports. CX Codex +1 644installs review-team cline review-team runs several independent reviewers against the same change. Useful when you want more than one perspective instead of a single pass. CX Codex +1 4,200installs team-polish Donchitos The team-polish skill coordinates subagents to polish a game feature or area, covering performance, visuals, audio, and QA checks. CX Codex +1 662installs ai-team-orchestration official github ai-team-orchestration is a GitHub Copilot skill that coordinates project work across agents for planning, implementation, and optional QA. It activates when starting a project, dividing up work, or resuming a session from saved context. CX Codex +1 381installs development-team mvschwarz development-team coordinates building and QA inside a development pod. It guides agents to deliver working code verified against public contracts. CX Codex +1 ★ 8,928repo stars red-team gaasher red-team finds weaknesses in content filters, classifiers and APIs through adversarial stress-testing — generates attack inputs and builds a catalogue of failures. CX Codex +1 ★ 185repo stars purple-team gaasher purple-team runs attack and defense as one loop: red-team finds failure classes in a filter or prompt you own, blue-team patches it, a fresh pass checks the patch. Repeat until dry. CX Codex +1 ★ 185repo stars

From the same set25

The whole set →
brand brand is a Claude Code subagent that designs logos and visual identity. It handles the whole pipeline from brief and SVG marks to favicons and brand guidelines. CX Codex ★ 71repo stars orchestrator orchestrator is a Claude Code subagent that moves an idea through a team pipeline from research to launch. It delegates each stage and waits for approval before continuing. CX Codex ★ 71repo stars team-docs team-docs is a Claude Code skill for writing technical documentation. It guides work on README files, API references, usage guides, and architecture notes. CX Codex +1 ★ 71repo stars team-prd team-prd is a Claude Code skill that structures product requirements documents for version 1 releases. Defines scope boundaries and testable acceptance criteria. CX Codex +1 ★ 71repo stars team-ux team-ux is a Claude Code skill that writes structured UX design specifications covering user flows, screen states, component catalogs, accessibility rules, and mobile behavior. CX Codex +1 ★ 71repo stars team-marketing team-marketing is a Claude Code skill for planning product marketing and launches, from positioning to a publishing calendar. It guides requests for channel plans, launch copy, and measurable goals. CX Codex +1 ★ 71repo stars team-market-research team-market-research is a Claude Code skill that structures market, competitor, and user research. Guides niche validation, source hierarchy checks, and product risk evaluations. CX Codex +1 ★ 71repo stars team-architecture team-architecture is a Claude Code skill for planning software architecture, from data models and API contracts to module boundaries and risks. It activates for architecture design requests. CX Codex +1 ★ 71repo stars

Project sponsors

Companies that keep this analytics open