complete-task

Finalizes a feature branch and merges its pull request to main.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/mistakenot/skills --skill complete-task-mistakenot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: complete-task
Source: https://github.com/mistakenot/skills/tree/main/plugins/planning-workflow/skills/complete-task
Command: npx skills add https://github.com/mistakenot/skills --skill complete-task-mistakenot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Shipping a finished task involves many easy-to-forget steps: resolving leftover PR feedback, running the right tests, writing retrospective feedback, merging, and cleaning up the worktree. This Skill walks through that entire finalization checklist so nothing is skipped before a branch lands on main. ## Core Features & Use Cases - Pre-merge verification: Checks prerequisites (feature branch, clean tree, open PR), resolves outstanding review threads via the address-feedback skill, and runs typecheck plus affected unit and E2E tests. - Structured feedback capture: Creates a feedback.md retrospective from a template covering problems faced, reflections, and useful context, then commits it before merging. - Merge and cleanup: Squash-merges the PR with gh pr merge --squash --delete-branch, exits the worktree, pulls latest main, and verifies the squashed commit landed. - Use Case: After executing a planned task in an isolated worktree and getting PR approval, invoke this Skill to ship the branch with a complete audit trail. ## Quick Start Complete and merge the current task branch after all PR feedback is addressed.

Frequently Asked Questions about complete-task

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

FAQPage Schema
How do I merge a feature branch PR from the command line?▼

Use `gh pr merge --squash --delete-branch` from the GitHub CLI to squash-merge the pull request and delete the remote branch in one step. This Skill runs that command only after feedback is resolved and tests pass.

What checks should run before merging a pull request?▼

Run a typecheck always, unit tests if test files changed, and E2E tests if frontend or server functions changed. All must pass, and any unresolved review threads should be addressed before merging.

What prerequisites does the complete-task skill require?▼

You must be on a feature branch (not main), have a clean working tree with no uncommitted changes, and have an open PR for the branch. If any prerequisite fails, the skill reports which one and stops.

How do I clean up a git worktree after merging a PR?▼

Shut down worktree-local services like dev servers and watchers, switch back to the main working tree, then run `git pull` and verify the squashed commit appears in `git log` with key files present.

Why write a feedback.md file before merging a task?▼

The feedback.md retrospective captures problems faced, reflections, and useful context while they are fresh, creating a reusable record for future tasks. It is committed and pushed to the branch before the squash merge.