Finish Work - Pre-Commit Checklist

Validate code changes with lint, type-check, and tests before committing.

2|Updated Jan 30, 2026

Search Tags:#code quality #testing #database migrations #pre-commit #spec synchronization #api changes

Ready to run

npx skills add https://github.com/LinXueyuanStdio/viben --skill finish-work-pre-commit-checklist

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Finish Work - Pre-Commit Checklist
Source: https://github.com/LinXueyuanStdio/viben/tree/main/packages/core/templates/codex/skills/finish-work
Command: npx skills add https://github.com/LinXueyuanStdio/viben --skill finish-work-pre-commit-checklist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents incomplete or inconsistent changes from being committed by ensuring code passes quality gates, relevant tests exist, specs and docs stay in sync, and cross-layer impacts are verified.

Core Features & Use Cases

Pre-commit quality verification: Runs linting, type-checking, and tests, and flags common issues like leftover console logs or unsafe TypeScript patterns.
Test and documentation completeness: Promotes adding unit/regression/integration tests when logic or behavior changes, and updating backend/frontend/spec documentation when needed.
Infra/cross-layer contract guardrails: Enforces stricter requirements (executable contracts, validation/error matrices, and required test points) when changes touch infrastructure or shared contracts.

Quick Start

Ask the AI to run the Finish Work checklist for your changes and tell you exactly which items you still need to address before committing.

Frequently Asked Questions about Finish Work - Pre-Commit Checklist

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

FAQPage Schema

How do I run a pre-commit checklist for code quality and tests?▼

A pre-commit checklist validates code quality by running pnpm lint, pnpm type-check, and pnpm test to ensure changes pass quality gates before committing. It flags leftover console logs, verifies type safety conventions, and checks cross-layer behavior.

What is spec synchronization and when do I need it before committing?▼

Spec synchronization ensures backend and frontend documentation stays consistent with code changes. You need it before committing when updates touch APIs, database migrations, or shared contracts to prevent incomplete cross-layer modifications.

How do I verify database migration correctness and API changes before committing?▼

To verify database migration correctness and API changes before committing, run a pre-commit validation that enforces executable contracts, validation matrices, and required test points for infrastructure updates to ensure cross-layer consistency.

Does this pre-commit workflow work with pnpm and TypeScript?▼

Yes, this pre-commit workflow explicitly requires pnpm to run lint, type-check, and test commands, while enforcing TypeScript type safety conventions and checking for unsafe patterns before allowing a commit.

What is the best way to ensure test completeness for bug fixes and API updates?▼

The best way to ensure test completeness is running a pre-commit check that promotes adding unit, regression, or integration tests whenever logic or behavior changes, verifying that all modified code paths are covered.

Why do I need to remove console logs before a git commit?▼

You need to remove console logs before a git commit because leftover debugging statements violate code quality conventions and can leak sensitive runtime data, which the pre-commit verification actively flags as an issue to block committing.