Run any Skill in Manus with one click

testing-quality-gate

Stars15

Forks0

UpdatedMarch 29, 2026 at 20:44

Run Amy's Echo testing and quality gates with clear evidence reporting. Use when preparing a change for commit/PR, diagnosing regressions, or deciding the minimum safe check set for touched webapp, server, or integration areas.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

voku

voku/AmysEcho

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

4 files

SKILL.md

readonly

name	testing-quality-gate
description	Run Amy's Echo testing and quality gates with clear evidence reporting. Use when preparing a change for commit/PR, diagnosing regressions, or deciding the minimum safe check set for touched webapp, server, or integration areas.

Testing Quality Gate

Select and execute the smallest complete test matrix that still protects Amy's communication reliability.

1) Choose the scope

Map touched files to packages:

webapp/ → webapp checks
server/ → server checks
integration/ or cross-stack flow → integration checks
docs-only → lightweight validation (links/scripts if available)

2) Run ordered checks

Start narrow, then widen:

Focused test file(s) for changed behavior.
Package type-check and lint.
Package full tests.
Build checks for deployable surfaces.
Integration tests for cross-stack or auth/profile workflow risk.

Use canonical commands from references/command-matrix.md.

3) Investigate failures before retry

Confirm whether failure is change-induced or pre-existing.
Capture first failing command and root-cause notes.
Prefer fixing nearby pre-existing issues when safely in scope.

4) Report evidence clearly

For each executed command, report pass/warning/fail and one-line context.

References

Command matrix: references/command-matrix.md
Failure triage template: references/failure-triage-template.md

More from this repository

same repository

amy-first-delivery

voku/AmysEcho

Apply Amy's Echo Amy-first delivery workflow for implementation and review tasks. Use when changing code, tests, or docs in this repository. Enforce discovery, planning, Amy-impact validation, and mandatory verification before merge.

2026-04-0515

model-training-workflow

voku/AmysEcho

Execute Amy's Echo model training workflows end-to-end with reproducible evidence. Use when changing trainer code, training metadata contracts, model artifact handling, few-shot evaluation, or release-readiness checks for training outputs.

2026-04-0515

express-zod-api-hardening

voku/AmysEcho

Build and harden Amy's Echo backend APIs using Express 5 and Zod contracts. Use when adding or modifying server routes, middleware, request validation, auth/profile checks, error handling, and response-shape guarantees.

2026-03-2915

identity-boundary-guard

voku/AmysEcho

Protect Amy's Echo account-versus-profile identity boundaries. Use when working on auth, settings, profile switching, uploads, training sync, or API flows where session/token and profileId can diverge.

2026-03-2915

mediapipe-tasks-vision-web

voku/AmysEcho

Implement and debug MediaPipe Tasks Vision gesture recognition in Amy's Echo webapp. Use when changing webcam capture, landmark extraction, gesture recognizer setup, model loading, runtime confidence logic, or detection diagnostics tied to MediaPipe behavior.

2026-03-2915

sign-language-ml-detection

voku/AmysEcho

Diagnose and improve Amy's Echo web sign-language ML detection quality. Use when working on MediaPipe landmarks, MLP inference thresholds, confidence/margin behavior, detector telemetry, fixture diagnostics, or profile-aware recognition regressions.

2026-03-2915

name	testing-quality-gate
description	Run Amy's Echo testing and quality gates with clear evidence reporting. Use when preparing a change for commit/PR, diagnosing regressions, or deciding the minimum safe check set for touched webapp, server, or integration areas.

Testing Quality Gate

Select and execute the smallest complete test matrix that still protects Amy's communication reliability.

1) Choose the scope

Map touched files to packages:

webapp/ → webapp checks
server/ → server checks
integration/ or cross-stack flow → integration checks
docs-only → lightweight validation (links/scripts if available)

2) Run ordered checks

Start narrow, then widen:

Focused test file(s) for changed behavior.
Package type-check and lint.
Package full tests.
Build checks for deployable surfaces.
Integration tests for cross-stack or auth/profile workflow risk.

Use canonical commands from references/command-matrix.md.

3) Investigate failures before retry

Confirm whether failure is change-induced or pre-existing.
Capture first failing command and root-cause notes.
Prefer fixing nearby pre-existing issues when safely in scope.

4) Report evidence clearly

For each executed command, report pass/warning/fail and one-line context.

References

Command matrix: references/command-matrix.md
Failure triage template: references/failure-triage-template.md