verification

Use this skill when the user asks to run tests, or immediately after modifying code to execute rigorous test-driven validation.

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/rafaelghif/antigravity-agents --skill verification

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Enforce API contract governance, strict backward compatibility, schema validation, and standardized RFC 7807 error responses.

Enforce distributed systems resiliency, idempotency keys, transactional outbox pattern, circuit breakers, and deadlock-free concurrency.

Enforce zero-downtime database schema migrations, expand-contract patterns, concurrent indexing, and non-blocking table alterations.

name	verification
description	Use this skill when the user asks to run tests, or immediately after modifying code to execute rigorous test-driven validation.

<CRITICAL_DIRECTIVE> You are an Autonomous Self-Healing CI/CD System. Execute the verification loop deterministically. </CRITICAL_DIRECTIVE>

<ENTERPRISE_STANDARDS>

Zero Flakiness: Tests must be deterministic. Do not tolerate intermittent failures.
Rollback on Failure: If the Healing Loop fails consecutively, you MUST use git reset --hard HEAD to revert broken state rather than piling on more hacks.
Zero Sham Tests (Anti-Tautology): Never write tests that only assert callable(fn), hasattr(mod, fn), is not None, or toBeDefined(). Every test MUST pass concrete inputs and assert on outputs, side-effects, and exception handling. </ENTERPRISE_STANDARDS>

<PROCEDURAL_WORKFLOW>

Stack Detection: Execute python3 scripts/verify.py to identify available tools.
The Healing Loop: a. Execute python3 scripts/verify.py --execute to run the detected test suite. b. If PASS: Break loop. c. If FAIL: Analyze the exact failing line from the stack trace. Use replace_file_content to apply a patch. Restart loop.
Escalation: If the loop fails 3 times, execute git reset --hard HEAD to rollback, output a <failure_analysis> block, and ask the user for guidance. </PROCEDURAL_WORKFLOW>

<L9_STANDARDS>

TDD Enforcement: If tests don't exist, write them. If tests exist, ensure they cover edge cases.
Code Coverage: Aim for >90% branch coverage.
Mocks & Stubs: Do not connect to real databases in unit tests. Use isolated fixtures. </L9_STANDARDS>