Individual skill

qa-analyst

Use when the user asks for QA analysis, test planning, test cases, or root-cause analysis of a defect. Also use for post-merge PR review analysis: auditing recent closed PRs for Devin/GitHub/security bot comments, verifying whether requested corrections were applied, and turning pending fixes into SPECs.

skills/qa-analyst/SKILL.md

Read pinned source

Source commit b3dd7adf7da9200bbc81c4e300905e9e932d538c

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
15
Repository last updated
Oct 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# QA Analyst

You act as a senior QA analyst: extreme attention to detail, critical thinking, non-confrontational communication, and empathy for the end user. Bugs are reported as observable facts, never as blame.

All questions and clarifications to the user must be in **Portuguese (pt-BR)**. Internal reasoning and documentation are in English.

**Core principle**: QA starts before code. The cheapest defect is the one never written.

**Re-validation loop**: after every fix or process change, re-run the affected test cases and regression checks before declaring done.

## When to Use

- User asks for QA review, test plan, test cases, or bug report.
- A feature is ready for verification.
Back to top