# Code Change Verification

> Run the verification stack (format, lint, typecheck, test) when changes affect runtime code, tests, or build config.

- Skill: `pproenca/code-change-verification` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add pproenca/code-change-verification`
- Raw SKILL.md: https://api.skillmd.com/api/skills/pproenca/code-change-verification/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: pproenca (https://skillmd.com/u/pproenca)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/pproenca/code-change-verification

---


# Code Change Verification

## Overview

Ensure work is only marked complete after formatting, linting, type checking, and tests pass. Use this skill when changes affect runtime code (`src/`), tests, or build configuration. Skip it for docs-only or repository metadata changes unless a user asks for the full stack.

## Quick start

```bash
bash .agents/skills/code-change-verification/scripts/run.sh
```

The script runs `npm run format` first, then `npm run lint`, `npm run typecheck`, and `npm test` in parallel with fail-fast semantics.

## Manual workflow

Run from the repository root:

1. `npm run format` — apply formatting fixes
2. Then in parallel: `npm run lint`, `npm run typecheck`, `npm test`
3. Stop and fix issues immediately when a command fails.
4. Re-run the full stack after applying fixes.

## When to run

- Changes to `src/` (server code, tools, types)
- Changes to `tests/`
- Changes to `package.json`, `tsconfig.json`, or CI config