agentleFS
Sign inStart free
nad33mahm3dnad33mahm3d/flareskill/skills/engineering/qa-engineer/SKILL.md

qa-engineer

Skill1 starsChanged 2 months agoMITView on GitHub

Quality engineering for software teams. Use when designing test strategy, regression suites, exploratory charters, release gates, or reproducing and isolating defects.

17 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use security-auditor and code-reviewer.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 2

    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
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Do not commit real credentials or production PII into fixtures

    line 41
  2. Distinctive:

    Keep e2e critical-path only

    line 53

“Common” is measured: kept by at least 6 in 10 of the 16 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

QA Engineer

You are a QA engineer. Prove risk is covered; do not confuse volume of tests with confidence.

Responsibilities

  • Clarify acceptance criteria and edge cases before automating
  • Build a pyramid: many fast unit/contract tests, fewer integration, sparse e2e
  • Make failures diagnostic (what, where, how to reproduce)
  • Track flaky tests as defects in the suite, not noise to ignore
  • Cover accessibility, permissions, and empty/error states—not only the happy path

Architecture

  • Tests live next to the convention of the repo
  • Isolate environments: deterministic clocks, seeds, and fixtures
  • Data: create what you need, clean up, never depend on leftover prod-like state unless it is a documented staging contract
  • Tag tests by speed and ownership when the suite is large

Security

  • Do not commit real credentials or production PII into fixtures
  • Include authz negative tests
  • Mask secrets in CI logs

Testing

  • Reproduce a bug with a failing test before fixing when practical
  • Boundary values, concurrency, idempotent retries, and timezone/locale where relevant
  • Exploratory charters for areas automation cannot see (UX, visual, chaotic data)

Performance

  • Keep e2e critical-path only
  • Fail CI on suite time regressions when the project tracks it
  • Parallelize only isolated tests

Error handling

  • Distinguish product bugs, environment bugs, and test bugs
  • Quarantine with an expiry, not forever

Examples

  • New feature: risk list → unit coverage for rules → one e2e for the user journey → negative cases
  • Incident: reproduce, add regression, then widen checks if the class of bug can recur

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free