finish-work

Enforce a pre-commit quality checklist for linting, type checks, and tests.

3.9k|339|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/zhukunpenglinyutong/desktop-cc-gui --skill finish-work-zhukunpenglinyutong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finish-work
Source: https://github.com/zhukunpenglinyutong/desktop-cc-gui/tree/main/.agents/skills/finish-work
Command: npx skills add https://github.com/zhukunpenglinyutong/desktop-cc-gui --skill finish-work-zhukunpenglinyutong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-commit quality gaps can slip through code changes; this checklist ensures linting, type checks, tests, and cross-layer verification before commits.

Core Features & Use Cases

  • Code Quality: ensure pnpm lint passes, pnpm type-check completes with no errors, and pnpm test passes; enforce no console.log and no non-null assertions or any types.
  • Code-Spec Sync & Infra Guardrails: keep code-spec docs up-to-date across backend/frontend components and enforce alignment with infrastructure and migrations checks.
  • Cross-Layer Verification: verify data flows through multiple layers, maintain type consistency, and validate error handling and loading states.
  • Manual Testing Ready: provide a structured checklist to validate feature behavior before final review.

Quick Start

Run the finish-work flow after finishing a feature to verify code quality, docs, and tests before committing.

Frequently Asked Questions about finish-work

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

FAQPage Schema
How do I enforce a pre-commit checklist for lint, type-check, and tests?

A pre-commit checklist enforces lint, type-check, and test validation before commits. This checklist requires `pnpm lint`, `pnpm type-check`, and `pnpm test` to pass, explicitly blocking commits with console.log, non-null assertions, or any types.

How do I verify cross-layer type consistency and data flows before committing?

Cross-layer verification validates data flows across multiple layers before committing. It maintains type consistency and validates error handling and loading states to eliminate incomplete code changes.

What's the best way to keep code-spec docs synchronized with infrastructure and migrations?

Keeping code-spec docs synchronized requires enforcing alignment with infrastructure and migrations checks. This pre-commit process updates backend and frontend component docs, ensuring code-spec sync before final review.

Can I use a pre-commit quality checklist for manual testing and feature validation?

Yes, a pre-commit quality checklist provides a structured manual testing checklist to validate feature behavior. It ensures code-spec alignment and cross-layer verification are ready before final review.

Why does my commit pass tests but still lack code-spec synchronization?

Passing tests does not guarantee code-spec synchronization. This checklist enforces backend and frontend component doc updates alongside test passes, blocking incomplete work where code and specs diverge.

Do I need to run pnpm lint and pnpm type-check separately before committing?

Running `pnpm lint` and `pnpm type-check` separately is unnecessary when using this checklist. It aggregates linting, type-checking, and tests into a single pre-commit flow with explicit pass/fail criteria.