Run any Skill in Manus with one click

pre-commit

Stars1,173

Forks27

UpdatedMay 23, 2026 at 03:24

Run the mandatory pre-commit checks for the poku repository before staging a commit. Use this whenever the user asks to commit, prepare a commit, push, open a PR, or verify a change is ready. Runs typecheck, lint:fix, build, and the local test suite in order, plus runtime-sensitive suites when the change touches runtime detection, isolation, child-process spawning, environment-variable plumbing, or any Bun or Deno specific code path.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

wellwelwel

wellwelwel/poku

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	pre-commit
description	Run the mandatory pre-commit checks for the poku repository before staging a commit. Use this whenever the user asks to commit, prepare a commit, push, open a PR, or verify a change is ready. Runs typecheck, lint:fix, build, and the local test suite in order, plus runtime-sensitive suites when the change touches runtime detection, isolation, child-process spawning, environment-variable plumbing, or any Bun or Deno specific code path.
user-invocable	true

Pre-commit

Guarantee that every commit lands with passing type checks, formatted code, a successful build, and a green local test suite, so no regression in correctness, style, or distributable output reaches the upstream history.

Preconditions

On a fork, read CONTRIBUTING.md first.
Working tree reflects the change under review (no unrelated edits staged).

Recommended steps

Run in this exact order. Any non-zero exit blocks the commit.

npm run typecheck: TypeScript type check across the project.
npm run lint:fix: auto-fixes Biome and Prettier. May modify files, which must be restaged.
npm run build: produces lib/ from src/.
npm test: full local Node.js suite.

Runtime-sensitive checks (conditional)

Run additionally when the change touches runtime detection, isolation, child-process spawning, environment-variable plumbing, or any Bun or Deno specific code path.

bun run test:bun: full local Bun suite.
deno task test:deno: full local Deno suite.

Running a subset

Direct execution of a single test file:

npx tsx <path> or npx tsx src/bin/index.ts <path>
bun --bun <path> or bun --bun src/bin/index.ts <path>
deno run -A <path> or deno run -A src/bin/index.ts --denoAllow=all <path>

Filter the suite by path:

npm test -- --filter=<path>
bun run test:bun -- --filter=<path>
deno task test:deno -- --filter=<path>

Acceptance criteria

All four mandatory steps exit with code 0.
Runtime-sensitive suites exit 0 when applicable.
Any files rewritten by lint:fix are restaged before commit, so no unstaged formatting deltas remain.

Failure modes

typecheck fails: fix the type error at its source. Do not relax tsconfig or add any to silence it.
lint:fix rewrites files: restage them and re-run from step 1. If a rule needs to be disabled, justify it in code review, not by skipping the step.
build fails: fix the underlying TypeScript or bundler error. The build catches issues npm test does not.
npm test fails: fix the test or the code under test. Never bypass with --no-verify or by skipping the test. Treat a modified existing test as a possible regression and prefer adding new tests.
Runtime-sensitive suite fails: reproduce locally with the failing runtime before pushing. A Node-only green run does not clear a runtime-sensitive change.

More from this repository

same repository

benchmarking

wellwelwel/poku

Empirical performance comparison playbook for poku covering hypothesis lenses, a standalone harness with a byte-identical correctness gate, variant generation, sequential hyperfine measurement, composition re-testing, and anomaly forensics. Use when measuring, comparing, or proving the performance of any project logic, when the user asks for benchmarks or optimization validation, or when a micro-optimization claim needs evidence before touching src/.

2026-06-101.2k

documentation

wellwelwel/poku

Documentation deep-dive for the poku website covering Docusaurus setup, language policy, feature-to-docs mapping, conventions, JSDoc, and the changelog. Use when editing or adding docs or mapping a feature to its page.

2026-06-021.2k

testing

wellwelwel/poku

Testing deep-dive for poku covering test structure, commands, patterns, fixtures, utils, Docker compatibility, and coverage. Use when writing, organizing, or running tests, adding fixtures, or working on coverage.

2026-05-201.2k

architecture

wellwelwel/poku

Architecture deep-dive for poku covering project structure, execution flow, config discovery, runtime detection, and competitive context. Use when navigating the codebase or understanding how components fit together.

2026-05-161.2k

engineering

wellwelwel/poku

Engineering deep-dive for poku covering performance, code, and security patterns, TypeScript config, build pipeline, developer experience, and CI/CD. Use when implementing or optimizing code, writing performance-sensitive logic, touching the build, or applying code-style and security rules.

2026-05-161.2k

name	pre-commit
description	Run the mandatory pre-commit checks for the poku repository before staging a commit. Use this whenever the user asks to commit, prepare a commit, push, open a PR, or verify a change is ready. Runs typecheck, lint:fix, build, and the local test suite in order, plus runtime-sensitive suites when the change touches runtime detection, isolation, child-process spawning, environment-variable plumbing, or any Bun or Deno specific code path.
user-invocable	true

Pre-commit

Preconditions

On a fork, read CONTRIBUTING.md first.
Working tree reflects the change under review (no unrelated edits staged).

Recommended steps

Run in this exact order. Any non-zero exit blocks the commit.

npm run typecheck: TypeScript type check across the project.
npm run lint:fix: auto-fixes Biome and Prettier. May modify files, which must be restaged.
npm run build: produces lib/ from src/.
npm test: full local Node.js suite.

Runtime-sensitive checks (conditional)

Run additionally when the change touches runtime detection, isolation, child-process spawning, environment-variable plumbing, or any Bun or Deno specific code path.

bun run test:bun: full local Bun suite.
deno task test:deno: full local Deno suite.

Running a subset

Direct execution of a single test file:

npx tsx <path> or npx tsx src/bin/index.ts <path>
bun --bun <path> or bun --bun src/bin/index.ts <path>
deno run -A <path> or deno run -A src/bin/index.ts --denoAllow=all <path>

Filter the suite by path:

npm test -- --filter=<path>
bun run test:bun -- --filter=<path>
deno task test:deno -- --filter=<path>

Acceptance criteria

All four mandatory steps exit with code 0.
Runtime-sensitive suites exit 0 when applicable.
Any files rewritten by lint:fix are restaged before commit, so no unstaged formatting deltas remain.

Failure modes

typecheck fails: fix the type error at its source. Do not relax tsconfig or add any to silence it.
lint:fix rewrites files: restage them and re-run from step 1. If a rule needs to be disabled, justify it in code review, not by skipping the step.
build fails: fix the underlying TypeScript or bundler error. The build catches issues npm test does not.
npm test fails: fix the test or the code under test. Never bypass with --no-verify or by skipping the test. Treat a modified existing test as a possible regression and prefer adding new tests.
Runtime-sensitive suite fails: reproduce locally with the failing runtime before pushing. A Node-only green run does not clear a runtime-sensitive change.