code-change-verification

name	code-change-verification
description	Run the repository verification stack after substantive changes to Rust code, JS/TS code, tests, build behavior, diagnostics, or local DB scripts. Trigger near the end of a task, not at initial planning time.

Code Change Verification

Goal

Run the standard verification stack and report exactly what passed, what failed, and what was skipped.

Use this when

• Runtime Rust code changed.
• JS/TS extraction or bridge code changed.
• Tests, fixtures, or diagnostics changed.
• Build scripts or package configuration changed.
• Local Postgres scripts or docker-compose files changed.

Run this script first

bash .agents/skills/code-change-verification/scripts/verify.sh

Reporting format

Report four sections:

1. Rust checks
2. JS/TS checks
3. DB / integration checks
4. Skipped checks and why

Rules

• Do not claim verification succeeded unless the command actually completed successfully.
• If a command is unavailable, report it as skipped with the missing dependency.
• If the repository has more specific commands, prefer those over inventing alternatives.
• If DB-assisted analysis code changed, also mention whether local PostgreSQL integration was exercised.
• Keep the output short and factual.

Notes

• This skill is explicit by design. Call it after meaningful code work.
• If the repository grows stricter commands later, update scripts/verify.sh rather than duplicating steps in prompts.