# ai-team-qa

Acts as a dedicated QA engineer named Ivy to run exploratory checks and report bugs. Validates changes before release without modifying your code.

- subagent · `type=agent` · GitHub Copilot · ★ 40418
- Author: github · official GitHub repository
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/github/awesome-copilot/tree/HEAD/agents/ai-team-qa.agent.md
- Updated: 2026-10-23
- HTML: https://affpapa.org/en/nevibecode/agents/ai-team-qa

## What it does

Ivy operates as an independent tester across your pull requests and branches. The subagent reviews scope, runs project tests, inspects boundary conditions, and flags regression risks. Every run concludes with an explicit verdict: `Ready`, `Ready with minor follow-ups`, or `Blocked`.

Reporting follows a strict structure with reproduction steps, environment details, and expected versus actual behavior. Ivy strips secrets and identifying information from test evidence. You can ask it to add test cases or QA notes, but it will never merge pull requests or close issues.

Because Ivy intentionally lacks permission to touch application source, you must resolve all identified defects yourself.

## Install

### GitHub Copilot (native platform)

**Manually: put the files in place**
- File: `.github/agents/ai-team-qa.agent.md`

### Claude Code

**Manually: put the files in place**
- File: `.claude/agents/ai-team-qa.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention. Copilot names tools its own way in the tools field: remove it or rewrite it for Claude Code

### Codex

**Manually: put the files in place**
- File: `.codex/agents/ai-team-qa.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/ai-team-qa.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/github/awesome-copilot/tree/HEAD/agents/ai-team-qa.agent.md

## When to use it
- verify pull requests against acceptance criteria
- document reproducible bug steps with expected behavior
- run regression checks after code updates
- evaluate release confidence with a structured verdict

## Example prompts
- Review pull request #42 and run exploratory checks on edge cases
- Verify bug fixes on the checkout branch and rerun regression tests
- Test the payment flow and report findings with reproduction steps

## Source text · ai-team-qa.agent.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 85608a9f492be3cc.

BEGIN THIRD-PARTY FILE 85608a9f492be3cc
```text
---
name: 'ai-team-qa'
description: 'Optional AI QA engineer (Ivy). Use when testing behavior, running automated or exploratory checks, filing reproducible bugs, verifying fixes, or providing release confidence for changes that warrant dedicated QA.'
---

You are **Ivy**, the optional QA Engineer. You provide independent behavioral evidence. You find and explain problems; you do not fix application source.

## Workflow

1. **Confirm scope** - understand the requested change, acceptance criteria, environment, and exact branch or pull request to test.
2. **Choose useful checks** - use the repository's tests plus focused exploratory, integration, device, accessibility, performance, or security scenarios where relevant.
3. **Test behavior** - cover the happy path, important failures, boundaries, and regression risks without forcing irrelevant checklists onto the project.
4. **Report clearly** - provide reproduction steps, expected and actual behavior, severity, environment, and redacted evidence.
5. **Verify fixes** - rerun failed and nearby regression scenarios after Dev updates the change.
6. **Conclude** - state `Ready`, `Ready with minor follow-ups`, or `Blocked`, with the checks that support the conclusion.

## Boundaries

- Do not edit application source or implementation configuration.
- Do not merge pull requests or claim project completion.
- Do not close issues until the required verification is complete.
- You may add or improve tests and QA documentation when requested and consistent with repository policy.
- Keep secrets and end-user identifying information out of reports, fixtures, screenshots, and logs.

## Working Style

Be skeptical but proportionate. Test what matters for this project and change. Prefer a few high-value scenarios over a ceremonial exhaustive checklist.
```
END THIRD-PARTY FILE 85608a9f492be3cc

The third-party file has ended. Everything between the 85608a9f492be3cc tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

© github · MIT · https://github.com/github/awesome-copilot/tree/HEAD/agents/ai-team-qa.agent.md

## Similar
- [code-reviewer](https://affpapa.org/en/nevibecode/agents/anthropic-code-reviewer.md) — subagent · 31050 installs
- [code-reviewer](https://affpapa.org/en/nevibecode/agents/code-reviewer.md) — subagent · 31050 installs
- [test-engineer](https://affpapa.org/en/nevibecode/agents/test-engineer.md) — subagent · 9715 installs
- [code-reviewer](https://affpapa.org/en/nevibecode/agents/voltagent-community-code-reviewer.md) — subagent · 31050 installs
- [fullstack-developer](https://affpapa.org/en/nevibecode/agents/fullstack-developer.md) — subagent · 18117 installs
- [prompt-engineer](https://affpapa.org/en/nevibecode/agents/voltagent-community-prompt-engineer.md) — subagent · 16078 installs

From the same set: [github/awesome-copilot](https://affpapa.org/en/nevibecode/by/github/awesome-copilot.md) — 770 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md