finish-work

Validate linting, type-checking, tests, and documentation before a git commit.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often forget to run linting, type‑checking, tests, and update documentation or database migrations before committing, leading to broken builds and undocumented changes.

Core Features & Use Cases

  • Comprehensive Checklist: Runs lint, type‑check, test suite, and verifies absence of console logs and unsafe TypeScript operators.
  • Spec Synchronization: Ensures backend, frontend, and cross‑layer specifications are up‑to‑date and contain executable contracts.
  • Cross‑Layer Verification: Validates API changes, database migrations, and manual testing before the commit is allowed.
  • Use Case Example: Before pushing a feature that modifies both API endpoints and database schema, invoke this skill to guarantee all quality gates and documentation are satisfied.

Quick Start

Invoke the finish-work skill to run the full pre‑commit checklist before committing your changes.

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 lint, type-check, and database migrations?

To run a pre-commit checklist, validate lint, type-check, tests, spec synchronization, API updates, and database migrations before committing. This blocks the commit if any check fails, ensuring code quality and documentation are satisfied.

What is cross-layer verification for API changes and database migrations?

Cross-layer verification validates API changes, database migrations, and manual testing before a git commit is allowed. It ensures backend, frontend, and cross-layer specifications are up-to-date and contain executable contracts.

How do I ensure spec synchronization before a git commit?

To ensure spec synchronization before a git commit, verify that backend, frontend, and cross-layer specifications are up-to-date and contain executable contracts. This prevents undocumented changes and broken builds.

Can I use this pre-commit validation for TypeScript and database schema changes?

Yes, pre-commit validation applies to TypeScript and database schema changes by verifying the absence of unsafe TypeScript operators, running type-checks, and ensuring database migrations exist before the commit is allowed.

What is the best way to block a git commit if tests fail?

The best way to block a git commit when tests fail is to run a comprehensive pre-commit checklist that validates lint, type-check, test suite passing, and spec synchronization, blocking the commit if any check fails.

Why does my pre-commit hook not catch missing database migrations?

A pre-commit hook may not catch missing database migrations if it lacks cross-layer verification. Implementing a comprehensive checklist ensures migrations exist and validates API changes before committing.