Skill

amoa-verification-patterns

Provides evidence-based verification patterns for code and systems, including exit code proofs, E2E testing, and integration checks. Generates pass/fail reports with reproducible evidence.

Python

Bash

npx claudepluginhub emasoft/ai-maestro-orchestrator-agent

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Evidence-based verification for proving code and systems work correctly. Collect measurable, reproducible evidence -- not assumptions.

Supporting Assets

SKILL.md

Similar Skills

verify

169

Runs parallel specialized agents to verify implementations, run tests (unit/e2e/integration/perf/LLM), grade quality (0-10 scale), and suggest improvements. Use before merging.

17 files21 tools

ork

strict-enforcement

121

Enforces strict code verification requiring runtime evidence like screenshots, curl responses, and CLI outputs beyond passing tests. Use for claudikins-kernel:verify, quality checks, pass/fail verdicts, and cross-command gates.

10 files9 tools

claudikins-kernel

dev-verify

Verifies feature completion by writing automated tests against SPEC.md, running commands for fresh evidence, and confirming outputs per Iron Law of Verification.

workflows

Stats

Stars10

Forks0

Last CommitApr 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Verification Patterns for AMOA

Overview

Evidence-based verification for proving code and systems work correctly. Collect measurable, reproducible evidence -- not assumptions.

Prerequisites

Python 3.8+, Bash, Git
Optional: Selenium (E2E), Docker (containerized tests), SQLite/PostgreSQL (integration)

Output

Verification reports with pass/fail status, collected evidence, and formatted results per test-report-format.md.

Core Patterns

Evidence-based -- evidence-based-verification.md

Exit code proof -- exit-code-proof.md

E2E testing -- end-to-end-testing.md

Integration -- integration-verification.md

Principles

See: verification-principles.md

Instructions

Select the appropriate verification pattern (evidence-based, exit code, E2E, or integration)
Set up the test environment per testing-protocol.md
Execute verification and collect measurable evidence
Format results per evidence-format.md and test-report-format.md
Report pass/fail with evidence; escalate failures immediately (fail-fast)
Update GitHub issues per github-integration.md and clean up test environment

Copy this checklist and track your progress:

Select pattern, set up environment
Execute verification, collect evidence
Format results, report pass/fail
Update GitHub issues, clean up

Examples

Input: Agent receives verification request for a new function. Output: Verification report with pass/fail, collected evidence, formatted results.

See examples.md for worked examples.

Resources

combining-patterns.md -- Combining patterns
- 5.1 Pattern Combinations
- 5.2 Verification Pyramid
- 5.3 Complete Verification Strategy Example
cross-platform-support.md -- Cross-platform
- 6.1 Platform-Specific Behavior
- 6.2 UTF-8 Encoding
- 6.3 Platform Detection
- 6.4 Path Handling
- ...
troubleshooting.md -- Troubleshooting
- 10.1 Tests Pass Locally but Fail in CI/CD
- 10.2 Exit Code is 0 but Process Failed
- 10.3 Integration Test Fails with Timeout
- 10.4 E2E Test is Flaky
- ...
docker-troubleshooting.md -- Docker
- 1. Assessing Docker Container Needs for a Project
- 1. Selecting Appropriate Base Images
- 1. Applying Docker Best Practices
- 1. Configuring Multi-Service Environments
- ...
quick-reference.md -- Quick reference & checklist
- Pattern Selection Guide
- Exit Codes
- Output Format
- Error Handling
- ...

Error Handling

Fail-fast: failures propagate immediately, no fallbacks. See troubleshooting.md and docker-troubleshooting.md in Resources.