finish-work

Validate linting, type checks, tests, API schemas, and migrations before commits.

3|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/BaSui01/agentflow --skill finish-work-basui01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finish-work
Source: https://github.com/BaSui01/agentflow/tree/main/.agents/skills/finish-work
Command: npx skills add https://github.com/BaSui01/agentflow --skill finish-work-basui01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevent incomplete or unsynchronized commits by verifying code quality, tests, documentation, API/schema updates, and database migrations before changes are committed.

Core Features & Use Cases

  • Comprehensive Pre-Commit Verification: Validate linting, type checks, and tests as gate criteria to reduce regressions.
  • Code-Spec and Cross-Layer Enforcement: Require executable infra and cross-layer specifications with signatures, validation matrices, example cases, and required tests.
  • API and Database Safeguards: Confirm API input/output schemas, client updates, migration files, and related queries are present and consistent.
  • Use Case: Before pushing a feature branch that touches frontend, backend, or infra contracts, run this checklist to block commits until contracts, docs, tests, and migrations are reconciled.

Quick Start

Run the finish-work checklist to validate linting, types, tests, executable specs, API changes, and migrations 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 prevent incomplete commits with missing database migrations or API schema updates?

To prevent incomplete commits, enforce a pre-commit checklist that validates database migrations and API schema updates. This verification blocks commits when mandatory artifacts like migration files or API input/output schemas are missing or inconsistent across layers.

What does a pre-push checklist enforce for code quality and cross-layer specs?

A pre-push checklist enforces code quality by requiring passing linting, type-checks, and tests. It also validates executable cross-layer specs by checking for signatures, validation matrices, example cases, and required tests before allowing a commit.

How do I validate frontend, backend, and infra contracts before pushing a feature branch?

Validate frontend, backend, and infra contracts by running a comprehensive pre-commit checklist. This process reconciles contracts, docs, tests, and migrations, ensuring that linting, type-checks, and executable specifications pass before the feature branch is pushed.

Can I use a pre-commit checklist to block commits when cross-layer tests and documentation are missing?

Yes, you can block commits when cross-layer tests and documentation are missing. The checklist requires executable infra specifications and verifies that client updates and related queries are present, preventing unsynchronized changes from being committed.

When do I need to verify API changes and database migrations during pre-commit workflows?

You need to verify API changes and database migrations during pre-commit workflows whenever changes touch frontend, backend, or infra contracts. This ensures API schemas, client updates, and migration files are consistent and present before committing.