finish

Verify passing tests and present integration options after code completion.

5|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/jstoup111/ai-conductor --skill finish-jstoup111
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finish
Source: https://github.com/jstoup111/ai-conductor/tree/main/skills/finish
Command: npx skills add https://github.com/jstoup111/ai-conductor --skill finish-jstoup111

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of verifying that all tests pass after implementation is complete, presenting options for integration, and handling cleanup.

Core Features & Use Cases

  • Fresh Verification: Ensures completion claims are backed by fresh evidence and presents structured options for integrating the work.
  • Push Direction: Proves remote staleness before force-pushing, preventing overwriting of other writers' work.
  • Review Changes: Provides a summary of changes before presenting options.
  • Present Options: Offers to merge locally, push and create a PR, keep as-is, or discard changes.
  • Execute Choice: Executes the chosen option and records the outcome.
  • Cleanup: Handles branch and worktree cleanup after execution.

Quick Start

Use the finish skill to mark a feature as complete, ensuring all tests pass and presenting integration options.

Frequently Asked Questions about finish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate test verification before pushing code changes?

Automating test verification requires a clean git status and successful test suite execution before presenting structured options for integrating work. This ensures completion claims are backed by fresh evidence.

What's the best way to present code integration options after a feature is complete?

Presenting code integration options involves reviewing a summary of changes and offering choices to merge locally, push and create a PR, keep as-is, or discard changes.

How can I prevent overwriting remote work when force-pushing git branches?

Preventing overwriting remote work requires proving remote staleness before force-pushing. This verifies the remote state and prevents overwriting other writers' contributions.

Does automated code completion require a clean git status?

Automated code completion requires a clean git status. The process will not proceed unless the working directory is clean and the test suite executes successfully.

How do I handle branch and worktree cleanup after merging code?

Handling branch and worktree cleanup is executed automatically after you choose an integration option. The skill executes the chosen action, records the outcome, and performs the cleanup.

What options do I have for integrating completed code in an SDLC workflow?

Integrating completed code in an SDLC workflow offers options to merge locally, push and create a pull request, keep the changes as-is, or discard them entirely.