finish-work

Validate linting, type checks, tests, migrations, and spec synchronization before committing.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/MaplumeX/deepresearch --skill finish-work-maplumex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finish-work
Source: https://github.com/MaplumeX/deepresearch/tree/main/.agents/skills/finish-work
Command: npx skills add https://github.com/MaplumeX/deepresearch --skill finish-work-maplumex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents incomplete, undocumented, or unsafely deployed changes from entering the codebase by enforcing a structured pre-commit quality checklist that covers linting, type checks, tests, spec synchronization, API and database changes, cross-layer verification, and manual testing.

Core Features & Use Cases

  • Comprehensive Code Quality Gates: Validates linting, type checking, test passing, and removal of debug artifacts to reduce regressions and noisy logs.
  • Spec and Cross-Layer Enforcement: Ensures code-spec documents are updated with executable signatures, validation matrices, and test cases, and blocks completion when infra or cross-layer specs remain abstract.
  • API & Database Change Verification: Confirms input/output schemas, client updates, migration files, and related queries are created and documented.
  • Use case: After implementing a feature that touches frontend components, backend endpoints, and a database schema, run the checklist to guarantee migrations exist, API and client schemas match, spec docs include concrete examples, and manual browser tests pass before committing.

Quick Start

Run the finish-work checklist on the current branch to validate linting, type checking, tests, migrations, API/schema updates, and spec synchronization 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 run a pre-commit checklist for code quality and database migrations?

To run a pre-commit checklist for code quality, validate linting, type checking, and tests, then verify database migration files and API schema updates are present before committing changes.

What is a pre-commit code quality gate and how does it work?

A pre-commit code quality gate prevents incomplete changes from entering the codebase by enforcing structured validation of linting, type checks, tests, API schemas, and spec synchronization before a commit is allowed.

How do I ensure spec synchronization with executable examples before committing?

To ensure spec synchronization with executable examples, update code-spec documents with executable signatures, validation matrices, and test cases, blocking commits when infra or cross-layer specs remain abstract.

How to verify API and database schema changes across frontend and backend layers?

To verify API and database schema changes across frontend and backend layers, confirm input and output schemas match, client updates are documented, and required migration files are created before committing.

Does pre-commit validation work for cross-layer development scenarios?

Pre-commit validation works for cross-layer development scenarios by validating coordinated changes spanning frontend, backend, API, and database layers, blocking completion when cross-layer specs lack necessary detail.

When should I block a commit due to missing cross-layer specs?

You should block a commit due to missing cross-layer specs when infra or cross-layer specification documents remain abstract and lack executable signatures, validation matrices, or concrete test cases.