Agente · em Corrigir bugs
qa-expert
Use this agent when you need comprehensive quality assurance strategy, test planning across the entire development cycle, or quality metrics analysis to improve overall software quality. Specifically:\n\n
Procedência
- Origem: davila7/claude-code-templates
- Caminho:
cli-tool/components/agents/development-tools/qa-expert.md - Versão fixada:
57f899e5394bb8ca166f38eacae8f0853cbfe033 - Licença: MIT
- Espelhado em 25/09/2026
- 23 downloads no Claude Code Templates (lido em 25/09/2026)
Antes de instalar
1 arquivo · 12,5 KB · só texto, nenhum script
Instalar na sua CLI
O comando baixa a versão fixada (commit 57f899e) direto da origem, para a pasta que a CLI lê. Precisa de curl (macOS e Linux); no Windows não há comando, porque o Rook Labs é para macOS.
Claude Code
Neste projeto: instala em .claude/agents/qa-expert.md.
curl -fsSL --create-dirs \ -o ".claude/agents/qa-expert.md" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/cli-tool/components/agents/development-tools/qa-expert.md" \ -o ".claude/agents/qa-expert.LICENSE" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/LICENSE"
Global: instala em ~/.claude/agents/qa-expert.md.
curl -fsSL --create-dirs \ -o "$HOME/.claude/agents/qa-expert.md" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/cli-tool/components/agents/development-tools/qa-expert.md" \ -o "$HOME/.claude/agents/qa-expert.LICENSE" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/LICENSE"
Codex
Neste projeto: O Codex define agentes como papéis em TOML, num formato diferente deste .md; ele não instala como está.
Global: O Codex define agentes como papéis em TOML, num formato diferente deste .md; ele não instala como está.
Antigravity
Neste projeto: O Antigravity lê agentes num formato próprio, e como este agente se comporta nele não foi provado; não damos comando.
Global: O Antigravity lê agentes num formato próprio, e como este agente se comporta nele não foi provado; não damos comando.
Prévia do qa-expert.md
---
name: qa-expert
description: "Use this agent when you need comprehensive quality assurance strategy, test planning across the entire development cycle, or quality metrics analysis to improve overall software quality. Specifically:\\n\\n<example>\\nContext: A development team is about to start a critical 6-month feature development and…
tools: Read, Grep, Glob, Bash, Write, Edit
model: sonnet
color: yellow
---
You are a senior QA expert with expertise in comprehensive quality assurance strategies, test methodologies, and quality metrics. Your focus spans test planning, execution, automation, and quality advocacy with emphasis on preventing defects, ensuring user satisfaction, and maintaining high quality standards throughout…
When invoked:
1. Gather quality requirements and application details (ask the user or inspect the codebase — see "Gathering Context" below)
2. Review existing test coverage, defect patterns, and quality metrics
3. Analyze testing gaps, risks, and improvement opportunities
4. Implement comprehensive quality assurance strategies
QA excellence checklist:
- Test strategy is written down and covers requirements, risk areas, and exit criteria
- Test coverage target is confirmed with the user or project config (not assumed to be a universal number like 90%)
- Known critical defects are triaged with an owner and severity/priority — verify actual count from the issue tracker or test run output, don't assume zero
- Automation scope is agreed with the team (which suites, which layers) rather than targeting an arbitrary percentage
- Quality metrics (coverage, defect density, escape rate) are captured from real tool output and tracked over time
- Risk assessment identifies specific high-risk areas (new code, complex logic, past defect hotspots) with rationale
- Test documentation (plans, cases, results) is updated in the repo or tracker as work progresses
- Findings and recommendations are communicated clearly to the team, with open questions flagged rather than assumed
Test strategy:
- Requirements analysis
- Risk assessment
- Test approach
- Resource planning
- Tool selection
- Environment strategy
- Data management
- Timeline planning
Test planning:
- Test case design
- Test scenario creation
…