finish-work

Name: finish-work
Availability: InStock
Author: yizhitangtongxue

Validates code quality, spec sync, and cross-layer changes before commits.

Updated Mar 24, 2026

Search Tags:#code quality #checklist #verification #pre-commit #lint #spec sync #type-check

Ready to run

npx skills add https://github.com/yizhitangtongxue/opencode-switch --skill finish-work-yizhitangtongxue

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: finish-work
Source: https://github.com/yizhitangtongxue/opencode-switch/tree/main/.agents/skills/finish-work
Command: npx skills add https://github.com/yizhitangtongxue/opencode-switch --skill finish-work-yizhitangtongxue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents incomplete work from being committed by enforcing a structured pre-commit checklist covering code quality, documentation sync, API changes, database migrations, and manual testing. ## Core Features & Use Cases - Code Quality Gates: Runs lint, type-check, and tests, and flags console.log statements, non-null assertions, and any types. - Code-Spec Sync Enforcement: Blocks completion when infra or cross-layer changes lack executable spec documentation with signatures, error matrices, and test cases. - Change-Type Checklists: Provides targeted verification steps for API changes, database schema changes, and cross-layer data flows. - Use Case: After fixing a bug that touched both frontend and backend, run this checklist to confirm types are consistent across layers, the spec docs are updated, and all tests pass before committing. ## Quick Start Ask the AI to run the finish-work pre-commit checklist on my current changes before I commit.

Frequently Asked Questions about finish-work

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

FAQPage Schema

How do I verify my code is ready to commit?▼

Run the pre-commit checklist covering lint, type-check, and tests, then verify documentation sync, API schema updates, and manual testing. The checklist blocks completion if infra or cross-layer changes lack executable spec documentation.

What should I check before committing database schema changes?▼

Confirm a migration file was created, the schema file is updated, related queries are adjusted, and seed data is refreshed if applicable. Missing migrations cause schema drift between environments.

When does the code-spec sync block a commit?▼

The block triggers when changes touch infrastructure or cross-layer contracts but the spec remains abstract. Specs must include real signatures, file paths, error matrices, Good/Base/Bad cases, and required test assertions.

Why does the checklist forbid console.log and any types?▼

Console.log statements create noisy production logs instead of using a proper logger, and any types bypass TypeScript safety guarantees. Both are flagged during the code quality section before commit.

What are the limitations of a manual pre-commit checklist?▼

A checklist relies on developer discipline and cannot automatically verify every item, such as manual browser testing or edge-case coverage. It complements but does not replace CI pipelines and automated hooks.