code-change-verification

Install dependencies, build, lint, typecheck, and test code changes.

Updated Aug 27, 2026

Search Tags:#verification #build #pnpm #lint #tests #code-change

Ready to run

npx skills add https://github.com/yuichi176/artlyst --skill code-change-verification

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-change-verification
Source: https://github.com/yuichi176/artlyst/tree/main/.codex/skills/code-change-verification
Command: npx skills add https://github.com/yuichi176/artlyst --skill code-change-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pnpm, git, and includes scripts (resource) components.

What problem does it solve?

This Skill ensures every code change goes through a full verification stack by installing dependencies, building, linting, typechecking (including generated declarations), and running tests to guarantee a clean, green state before merging.

Core Features & Use Cases

Automated dependency installation: Installs project dependencies to reproduce a fresh environment.
Deterministic verification pipeline: Builds, lints, typechecks, and tests run in a fixed order to ensure reliability.
Monorepo readiness: Works across multi-package repos by locating the repository root and applying the same checks.

Quick Start

macOS/Linux: bash .codex/skills/code-change-verification/scripts/run.sh
Windows (PowerShell): bash .codex/skills/code-change-verification/scripts/run.sh
If any command fails, fix the issue, re-run the script, and report the failing output.

Frequently Asked Questions about code-change-verification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify code changes before merging to ensure builds, tests, and linting pass?▼

Code-change verification automates end-to-end validation by installing dependencies, building, linting, typechecking, and running tests in a deterministic sequence. Run the verification script to produce a green state and catch issues before merge.

Can I use pnpm-based verification across monorepos with multiple packages?▼

Yes, this verification pipeline works across multi-package monorepos by locating the repository root and applying the same build, lint, typecheck, and test checks consistently to all packages.

What does the code-change verification pipeline actually check?▼

The pipeline installs dependencies, builds your project, runs linters, performs typechecking on generated declarations, and executes tests—each step in fixed order to ensure reliability and catch regressions.

Do I need to manually run build, lint, and test commands separately or can I automate them?▼

Automation runs the full verification stack—install, build, lint, typecheck, and tests—in one deterministic sequence. Use the provided script to execute all checks at once rather than running commands individually.

What should I do if the verification script fails during code-change checks?▼

Fix the failing step (dependency install, build, lint, typecheck, or test), re-run the script, and report the failing output so the issue is resolved before merging.

Does code-change verification work on macOS, Linux, and Windows?▼

Yes, the verification script runs on macOS and Linux using bash, and on Windows via PowerShell—execute the same script path across all platforms for consistent verification.