New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Finish Work

by jlifeng in jlifeng/JobPilot

“Finish Work - Pre-Commit Checklist”

— description from SKILL.md by jlifeng
Apache-2.0Auto-check passedDevelopment

Install Finish Work

skills CLI
$ npx skills add jlifeng/JobPilot --skill finish-work -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jlifeng/JobPilot finish-work --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jlifeng/JobPilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/finish-work .claude/skills/finish-work && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
finish-work
GitHub stars
140
Token cost
~1.1k tokens
SKILL.md length
413 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
Apache-2.0

At a glance

  • Works in 6 steps: Code Quality → Code-Spec Sync → API Changes → …
  • SKILL.md covers Checklist, Quick Check Flow, Common Oversights and Relationship to Other Commands, plus 1 more section
  • Calls pnpm and git

About this skill

Finish Work is a skill in jlifeng/JobPilot (140 stars). Its SKILL.md is about 1.1k tokens. Licence: Apache-2.0.

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Code Quality
  2. Code-Spec Sync
  3. API Changes
  4. Database Changes
  5. Cross-Layer Verification
  6. Manual Testing

What it can do on your machine

Read from SKILL.md and the folder at commit 7f33542. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pnpm
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pnpm and git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Finish Work loads about 1.1k tokens when it runs. Until then it costs about 12 tokens; SKILL.md has 413 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~12
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jlifeng/JobPilot at commit 7f33542, republished under its Apache-2.0 licence (© jlifeng). 413 words, ~1,050 tokens.

Download SKILL.mdSave it as .claude/skills/finish-work/SKILL.md (or your agent's skills folder).
name
finish-work
description
Finish Work - Pre-Commit Checklist

Finish Work - Pre-Commit Checklist

Before submitting or committing, use this checklist to ensure work completeness.

Timing: After code is written and tested, before commit

Checklist

1. Code Quality
bash
# Must pass
pnpm lint
pnpm type-check

# If the project defines a test script, it must pass too
pnpm test
  • pnpm lint passes with 0 errors?
  • pnpm type-check passes with no type errors?
  • If the project defines a test command, do tests pass?
  • No console.log statements (use logger)?
  • No non-null assertions (the x! operator)?
  • No any types?
2. Code-Spec Sync

Code-Spec Docs:

  • Does .trellis/spec/backend/ need updates?
    • New patterns, new modules, new conventions
  • Does .trellis/spec/frontend/ need updates?
    • New components, new hooks, new patterns
  • Does .trellis/spec/guides/ need updates?
    • New cross-layer flows, lessons from bugs

Key Question:

"If I fixed a bug or discovered something non-obvious, should I document it so future me (or others) won't hit the same issue?"

If YES -> Update the relevant code-spec doc.

2.5. Code-Spec Hard Block (Infra/Cross-Layer)

If this change touches infra or cross-layer contracts, this is a blocking checklist:

  • Spec content is executable (real signatures/contracts), not principle-only text
  • Includes file path + command/API name + payload field names
  • Includes validation and error matrix
  • Includes Good/Base/Bad cases
  • Includes required tests and assertion points

Block Rule: If infra/cross-layer changed but the related spec is still abstract, do NOT finish. Run $update-spec manually first.

3. API Changes

If you modified API endpoints:

  • Input schema updated?
  • Output schema updated?
  • API documentation updated?
  • Client code updated to match?
4. Database Changes

If you modified database schema:

  • Migration file created?
  • Schema file updated?
  • Related queries updated?
  • Seed data updated (if applicable)?
Show full SKILL.md (169 more words)Show less
5. Cross-Layer Verification

If the change spans multiple layers:

  • Data flows correctly through all layers?
  • Error handling works at each boundary?
  • Types are consistent across layers?
  • Loading states handled?
6. Manual Testing
  • Feature works in browser/app?
  • Edge cases tested?
  • Error states tested?
  • Works after page refresh?

Quick Check Flow

bash
# 1. Code checks
pnpm lint && pnpm type-check

# 1.5 Optional: if package.json defines a test script
pnpm test

# 2. View changes
git status
git diff --name-only

# 3. Based on changed files, check relevant items above

Common Oversights

OversightConsequenceCheck
Code-spec docs not updatedOthers don't know the changeCheck .trellis/spec/
Spec text is abstract onlyEasy regressions in infra/cross-layer changesRequire signature/contract/matrix/cases/tests
Migration not createdSchema out of syncCheck db/migrations/
Types not syncedRuntime errorsCheck shared types
Tests not updatedFalse confidenceRun full test suite
Console.log left inNoisy production logsSearch for console.log

Relationship to Other Commands

Development Flow:
  Write code -> Test -> $finish-work -> git commit -> $record-session
                          |                              |
                   Ensure completeness              Record progress
                   
Debug Flow:
  Hit bug -> Fix -> $break-loop -> Knowledge capture
                       |
                  Deep analysis
  • $finish-work - Check work completeness (this skill)
  • git commit / git push - Human executes by default; AI may do so only with explicit user authorization
  • $record-session - Record session and commits
  • $break-loop - Deep analysis after debugging

Core Principle

Delivery includes not just code, but also documentation, verification, and knowledge capture.

Complete work = Code + Docs + Tests + Verification

© jlifeng, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/finish-work of jlifeng/JobPilot.

Open the folder on GitHubat commit 7f33542

Compare with similar skills

Finish Work next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Finish Work compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Finish Work this skilljlifeng/JobPilot140—~1.1kAutomated safety check: PassApache-2.0
Vercel Composition Patternssupabase/supabase111k58 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Vercel Composition Patterns

    supabase/supabase

    Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 58 repos~726 tokens
    DevelopmentAuto-check passed

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

More from jlifeng/JobPilot

  • Brainstorm

    jlifeng/JobPilot

    Brainstorm - Requirements Discovery (AI Coding Enhanced). An agent skill from jlifeng/JobPilot.

    140 GitHub stars~3.1k tokensUpdated yesterday
    Auto-check passed

  • Update Spec

    jlifeng/JobPilot

    Update Code-Spec - Capture Executable Contracts. An agent skill from jlifeng/JobPilot.

    140 GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed

  • Break Loop

    jlifeng/JobPilot

    Break the Loop - Deep Bug Analysis

    140 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Start

    jlifeng/JobPilot

    Start Session

    140 GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Finish Work

How do I install Finish Work in Claude Code?

Run `npx skills add jlifeng/JobPilot --skill finish-work -a claude-code`. Or copy the skill folder (.agents/skills/finish-work in jlifeng/JobPilot) into .claude/skills/finish-work in your project. Claude Code loads it when a task matches its description.

How do I install Finish Work in Codex?

Run `npx skills add jlifeng/JobPilot --skill finish-work -a codex`. Or copy the skill folder (.agents/skills/finish-work in jlifeng/JobPilot) into .agents/skills/finish-work in your project. Codex loads it when a task matches its description.

Can I use Finish Work in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jlifeng/JobPilot --skill finish-work -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/finish-work, .gemini/skills/finish-work, .github/skills/finish-work and .opencode/skills/finish-work in your project.

What does Finish Work need to run?

Going by SKILL.md and its folder, Finish Work needs the command-line tools its instructions call (pnpm and git).

Does Finish Work access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Finish Work safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Finish Work use?

Finish Work is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Finish Work use?

About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Finish Work?

Skills that share tags, products or a category with Finish Work: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Finish Work?

jlifeng (a GitHub user) maintains it in jlifeng/JobPilot, which has 140 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 2026.

Source: jlifeng/JobPilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.