finish-work

Validate changes, run quality gates, commit, push, and create a pull request.

1|Updated Apr 17, 2025
One-click install
npx skills add https://github.com/carrot-foundation/schemas --skill finish-work-carrot-foundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finish-work
Source: https://github.com/carrot-foundation/schemas/tree/main/.cursor/skills/finish-work
Command: npx skills add https://github.com/carrot-foundation/schemas --skill finish-work-carrot-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end completion of a development task by coordinating validation, quality gates, commits, push, and PR creation.

Core Features & Use Cases

  • End-to-end wrap-up: validates changes, runs quality gates, commits changes, pushes the branch, and creates a pull request.
  • Guardrails: enforces branch naming conventions and requires all gates to pass before merging.
  • Use Case: when a task reaches completion, trigger a single command to finalize the work and begin review.

Quick Start

Run the finish-work workflow to finalize the task by validating, checking, committing, pushing, and opening a pull request.

Frequently Asked Questions about finish-work

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

FAQPage Schema
How do I automate the end-to-end git workflow for creating a pull request?

To automate the end-to-end git pull request workflow, you chain validation, quality gates, commits, pushes, and PR creation. This Skill orchestrates that sequence, guiding users through branch checks and merge prep deterministically.

What is the best way to enforce quality gates before merging a feature branch?

Enforcing quality gates before merging requires all validation checks to pass. This Skill enforces deterministic steps and ensures every gate passes before merging, preventing incomplete or unvalidated code from proceeding to the final pull request creation.

Can I enforce conventional branch naming conventions during task wrap-up?

Yes, enforcing conventional branch naming during task wrap-up is supported. The Skill applies guardrails to feature completion and code tasks across branches, ensuring branch naming conventions are checked before proceeding with commits and pushes.

Does this task wrap-up workflow require any external dependencies or components?

The task wrap-up workflow does not require external dependencies or components to operate. It orchestrates end-to-end task completion natively by coordinating validation, quality gates, commits, pushes, and pull request creation.

Why does my pull request creation fail when quality gates do not pass?

Pull request creation fails when quality gates do not pass because the workflow enforces deterministic steps and requires all gates to pass before merging. This guardrail ensures only fully validated code changes proceed to the final PR creation and review stage.