finish-work

Enforce pre-commit quality gates for linting, type-checking, tests, and documentation.

114|18|Updated May 15, 2026
One-click install
npx skills add https://github.com/jlifeng/JobPilot --skill finish-work-jlifeng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finish-work
Source: https://github.com/jlifeng/JobPilot/tree/main/.agents/skills/finish-work
Command: npx skills add https://github.com/jlifeng/JobPilot --skill finish-work-jlifeng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This checklist helps ensure code submissions meet quality gates before commit, reducing defects and review cycles.

Core Features & Use Cases

  • Pre-commit quality gates: lint, type-check, and tests must pass before commit.
  • Quality documentation: checks for console logs and type coverage to promote clean code.
  • Use Case: A solo developer or team can embed this in their workflow to maintain high standards before pushing changes.

Quick Start

Run the pre-commit checklist before committing to ensure all checks pass.

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 code quality by validating linting, type-checking, and tests before submissions. This ensures code meets quality gates, reducing defects and review cycles for individual or team workflows.

What is the best way to automate code quality checks before committing?

Automating code quality checks before committing involves running a tight pre-commit checklist. This validates lint, type-check, and test execution to catch defects early and maintain high standards before pushing changes.

Can I use a pre-commit quality gate for both solo and team workflows?

Pre-commit quality gates apply to both solo and team workflows. They validate linting, type-checking, tests, and documentation to ensure code submissions meet consistent quality standards regardless of team size.

How do I check for console logs and type coverage before a code commit?

Checking for console logs and type coverage before a commit is handled by a pre-commit checklist. It validates code quality and documentation to promote clean code before changes are submitted.

Do I need YAML frontmatter in SKILL.md to run a pre-commit checklist?

Standardized YAML frontmatter in SKILL.md with name and description is required to run the pre-commit checklist. Optional scripts, references, and assets can extend the behavior of the validation workflow.