skills.rest
ravenslight2010
ravenslight2010COMMUNITY
Explore all skills by this author →
GitHub

verify-before-commit

Validates repository changes with typecheck, lockfile sync, and CI gates before committing.

Updated Jun 15, 2026
Search Tags:#git#verification#pnpm#monorepo#pre-commit#ci#typecheck
One-click install
npx skills add https://github.com/ravenslight2010/Production-run-calculator --skill verify-before-commit-ravenslight2010
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-before-commit
Source: https://github.com/ravenslight2010/Production-run-calculator/tree/main/.agents/skills/verify-before-commit
Command: npx skills add https://github.com/ravenslight2010/Production-run-calculator --skill verify-before-commit-ravenslight2010

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents broken commits and false "green build" claims in a pnpm monorepo where local ARM machines cannot run the full test suite, so verification must follow a specific discipline before every commit or push. ## Core Features & Use Cases - Pre-commit verification checklist: Enforces a clean git status, root typecheck via CI=true pnpm run typecheck, and leaf typechecks for changed lib/* packages. - ARM-aware workarounds: Replaces pnpm run build and vitest with plain-node node -e logic checks, since non-x64 native binaries are stripped on this machine. - Lockfile and CI discipline: Keeps pnpm-workspace.yaml overrides in sync with the lockfile via pnpm install --frozen-lockfile, and defers the real test gate to the x64 CI workflow. - Use Case: Before pushing a change to the inventory math package, run the checklist to typecheck the leaf package, sanity-check edge cases in node, confirm the lockfile is current, then commit and watch the ci.yml workflow until green. ## Quick Start Ask the assistant to verify the current changes are ready to commit for this repo before pushing.

Frequently Asked Questions about verify-before-commit

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

FAQPage Schema
How do I verify changes before committing in a pnpm monorepo?▼

Run `CI=true pnpm run typecheck` at the root, confirm git status is clean, and run leaf typechecks for any changed lib packages. Commit only after these pass, then watch the CI workflow for the real test gate.

Why does pnpm run build fail locally but pass in CI?▼

The vite build requires workflow-provided PORT and BASE_PATH environment variables, so it fails outside CI. Use `CI=true pnpm run typecheck` for local verification instead of the build.

Can I run vitest or Playwright tests on an ARM machine?▼

No, this repo strips non-x64 native binaries, so vitest, vite, rollup, and Playwright cannot run on aarch64. Mirror pure logic in `node -e` for local sanity checks and rely on x64 CI runners for the full suite.

Why does pnpm install fail after editing pnpm-workspace.yaml?▼

Editing overrides, allowBuilds, or onlyBuiltDependencies makes the lockfile stale, causing `pnpm install` to exit 1. Run `CI=true pnpm install --frozen-lockfile` and commit the updated lockfile.

When should I add new tests to the repo?▼

Add tests only alongside real behavior changes or when explicitly requested. Empty test suites fail CI, so pass `--passWithNoTests` if a suite genuinely has nothing to run yet.

Related Skills

Explore More Software Engineering Skills→
prestariusprestarius
1

zoom-out

Explain unfamiliar code by mapping callers, dependencies, and subsystem boundaries.

Community
Intermediate
TomekNoconTomekNocon

check-and-commit

Run build, generation, i18n, typecheck, unit tests, and app build checks before committing and pushing.

Community
Advanced
dieguscldieguscl

docker-build

Build and test Docker images locally with security scanning.

Community
Intermediate
WanderWave-Travel-and-ToursWanderWave-Travel-and-Tours

run-wwtt-website

Runs, screenshots, and tests the WanderWave React/Vite frontend using a Playwright driver.

Official
Intermediate