Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

Commencer

eng-rigorous-validation

Étoiles2

Forks0

Mis à jour6 février 2026 à 04:08

Enforce reproducible testing, automated verification, and evidence-driven sign-off before merging any change.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

tjboudreaux

tjboudreaux/cc-plugin-engineering-excellence

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

SKILL.md

readonly

name	eng-rigorous-validation
description	Enforce reproducible testing, automated verification, and evidence-driven sign-off before merging any change.

Rigorous Validation

Intent

Ship only when behavior is proven, not assumed.
Treat tests, QA scripts, linters, and on-chain/off-chain simulations as first-class deliverables.
Capture evidence so reviewers can verify quickly.

Inputs

Canonical test commands (unit, integration, e2e, contract sims, UI snapshots).
Acceptance criteria plus measurable signals (logs, screenshots, transaction hashes).
Migrations/seed data steps required to exercise the change locally.

Workflow

Design tests before coding
- Specify failing cases and target assertions for each requirement.
- Align on how to stub external services, wallets, or platform APIs.
Automate and isolate
- Prefer deterministic, headless test harnesses; avoid manual-only steps.
- Seed data/fixtures close to tests to prevent global coupling.
Run the full relevant matrix
- Cover affected platforms (iOS/Android/web), runtimes, or chain environments.
- Capture artifacts (logs, screenshots, traces) for any non-deterministic checks.
Track outcomes
- Record exact commands run and their commit hash in the PR or issue.
- File follow-ups for flaky tests before merging.

Verification

All targeted tests green and documented; no TODOs or skipped suites without owner sign-off.
Static analysis, type-checking, formatters, and contract analyzers pass.
Evidence (artifacts, hashes, screenshots) attached or linked for reviewer inspection.

Plus depuis ce dépôt

même dépôt

eng-holistic-systems

tjboudreaux/cc-plugin-engineering-excellence

Model the end-to-end system, constraints, and failure modes before touching code; use whenever a change spans multiple layers or unclear requirements.

2026-02-062

eng-iterative-delivery

tjboudreaux/cc-plugin-engineering-excellence

Decompose work into safe, observable increments with feature flags, rollbacks, and communication baked in.

2026-02-062

eng-observability

tjboudreaux/cc-plugin-engineering-excellence

Design every change with traceability, diagnostics, and fast incident triage in mind across mobile, web, and web3 stacks.

2026-02-062

eng-performance

tjboudreaux/cc-plugin-engineering-excellence

Guard latency, memory, battery, bandwidth, and gas/compute budgets by measuring before and after every change.

2026-02-062

eng-quality-handoff

tjboudreaux/cc-plugin-engineering-excellence

Deliver changes with clear communication, reviewer-ready context, and follow-up accountability.

2026-02-062

eng-security-safety

tjboudreaux/cc-plugin-engineering-excellence

Apply proactive threat modeling, least-privilege design, and safety guardrails before delivering any code or infrastructure change.

2026-02-062

name	eng-rigorous-validation
description	Enforce reproducible testing, automated verification, and evidence-driven sign-off before merging any change.

Rigorous Validation

Intent

Ship only when behavior is proven, not assumed.
Treat tests, QA scripts, linters, and on-chain/off-chain simulations as first-class deliverables.
Capture evidence so reviewers can verify quickly.

Inputs

Canonical test commands (unit, integration, e2e, contract sims, UI snapshots).
Acceptance criteria plus measurable signals (logs, screenshots, transaction hashes).
Migrations/seed data steps required to exercise the change locally.

Workflow

Design tests before coding
- Specify failing cases and target assertions for each requirement.
- Align on how to stub external services, wallets, or platform APIs.
Automate and isolate
- Prefer deterministic, headless test harnesses; avoid manual-only steps.
- Seed data/fixtures close to tests to prevent global coupling.
Run the full relevant matrix
- Cover affected platforms (iOS/Android/web), runtimes, or chain environments.
- Capture artifacts (logs, screenshots, traces) for any non-deterministic checks.
Track outcomes
- Record exact commands run and their commit hash in the PR or issue.
- File follow-ups for flaky tests before merging.

Verification

All targeted tests green and documented; no TODOs or skipped suites without owner sign-off.
Static analysis, type-checking, formatters, and contract analyzers pass.
Evidence (artifacts, hashes, screenshots) attached or linked for reviewer inspection.