一键在 Manus 中运行任何 Skill

qa-engineer

Validate product changes against requirements using emulator-backed integration tests, regression checks, and release signoff criteria. Use when reviewing features, writing QA plans, expanding tests, or deciding ship readiness.

在 Manus 中运行

星标0

分支0

更新时间2026年3月21日 08:30

来源

khorzhenwin

khorzhenwin/tenxeng

打开 GitHub 仓库查看创作者相关仓库

安装命令

下载

在 Manus 中运行

适用职业SOC

软件质量保证分析师与测试员计算机与数学类职业15-1253L4

SKILL.md

readonly

name	qa-engineer
description	Validate product changes against requirements using emulator-backed integration tests, regression checks, and release signoff criteria. Use when reviewing features, writing QA plans, expanding tests, or deciding ship readiness.

QA Engineer

When To Use

Use this skill when you need to:

Turn acceptance criteria into a test plan
Review a feature for regressions or missing coverage
Add or expand integration tests
Decide whether a feature is ready to ship

Required Inputs

Read these first:

docs/product/<feature>/PRD.md
docs/product/<feature>/IMPLEMENTATION.md
docs/product/<feature>/QA.md

Then use:

integration-testing
integration-standards
Any domain skill referenced by the implementation

Default Workflow

Map each acceptance criterion to one or more checks.
Cover happy path, empty state, guardrail path, and regression-sensitive behavior.
Prefer integration tests in tests/integration/ for API-backed features.
Verify status codes, payload shape, and persisted Firestore outcomes when relevant.
Run lint and the relevant test suite before signoff.
Summarize blockers first, then residual risks, then what was verified.

Review Output Format

Use this order:

Findings and blockers
Coverage completed
Residual risks or gaps
Ship recommendation

Repo-Specific Guidance

Auth is typically mocked with setAuthedUser(...) in integration tests.
Route handlers are invoked directly with Request objects.
Firestore emulator data should be cleared between tests.
Keep status-code expectations aligned with shared API semantics.

Signoff Checklist

Acceptance criteria are covered.
Empty and error states were checked.
Relevant regressions were considered.
Tests are deterministic.
Lint/test commands were run or any gaps were called out explicitly.

Anti-Patterns

Do not:

Approve a feature based only on happy-path UI checks.
Skip persisted-data assertions for Firestore-backed flows.
Bury critical findings below summaries.
Leave residual risks undocumented at ship time.

同仓库更多 Skills

同仓库

product-market-fit-validator

khorzhenwin/tenxeng

Validate whether a proposed or shipped feature fits the product, solves a meaningful user problem, and stays differentiated from existing surfaces. Use when reviewing overlap between features, checking product market fit, challenging roadmap ideas, evaluating retention or adoption risk, or pressure-testing new UX against the current product.

2026-03-220

product-market-fit-validator

Implement approved product work across UI, API routes, shared libraries, and tests using this repo's feature packet and architecture conventions. Use when building features, integrating Firebase-backed flows, or coordinating delivery with PM and QA docs.

2026-03-210

product-manager

khorzhenwin/tenxeng

Drive feature requirements, scope, acceptance criteria, and cross-role handoff for this repo. Use when reviewing product gaps, writing PRDs, choosing MVP scope, defining success metrics, or synchronizing PM, engineering, and QA around a feature.

2026-03-210

firebase-integration

khorzhenwin/tenxeng

Standardize Firebase integration for this project across client SDK, Admin SDK, auth/session flows, Firestore usage, and environment variables. Use when adding or modifying Firebase auth, Firestore reads/writes, API routes touching Firebase, or Firebase-related setup.

2026-03-100

gemini-question-generation

khorzhenwin/tenxeng

Implement and maintain Gemini-powered question generation in this project using shared prompt, Zod parsing, model configuration, and robustness checks. Use when editing quiz generation, embeddings, Gemini API calls, prompt logic, or related API routes.

2026-03-100

name	qa-engineer
description	Validate product changes against requirements using emulator-backed integration tests, regression checks, and release signoff criteria. Use when reviewing features, writing QA plans, expanding tests, or deciding ship readiness.

QA Engineer

When To Use

Use this skill when you need to:

Turn acceptance criteria into a test plan
Review a feature for regressions or missing coverage
Add or expand integration tests
Decide whether a feature is ready to ship

Required Inputs

Read these first:

docs/product/<feature>/PRD.md
docs/product/<feature>/IMPLEMENTATION.md
docs/product/<feature>/QA.md

Then use:

integration-testing
integration-standards
Any domain skill referenced by the implementation

Default Workflow

Map each acceptance criterion to one or more checks.
Cover happy path, empty state, guardrail path, and regression-sensitive behavior.
Prefer integration tests in tests/integration/ for API-backed features.
Verify status codes, payload shape, and persisted Firestore outcomes when relevant.
Run lint and the relevant test suite before signoff.
Summarize blockers first, then residual risks, then what was verified.

Review Output Format

Use this order:

Findings and blockers
Coverage completed
Residual risks or gaps
Ship recommendation

Repo-Specific Guidance

Auth is typically mocked with setAuthedUser(...) in integration tests.
Route handlers are invoked directly with Request objects.
Firestore emulator data should be cleared between tests.
Keep status-code expectations aligned with shared API semantics.

Signoff Checklist

Acceptance criteria are covered.
Empty and error states were checked.
Relevant regressions were considered.
Tests are deterministic.
Lint/test commands were run or any gaps were called out explicitly.

Anti-Patterns

Do not:

Approve a feature based only on happy-path UI checks.
Skip persisted-data assertions for Firestore-backed flows.
Bury critical findings below summaries.
Leave residual risks undocumented at ship time.