asapp-close-task

Squash-merge a completed task branch into local main with verification.

Updated Apr 28, 2024
One-click install
npx skills add https://github.com/attrigo/asapp --skill asapp-close-task
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asapp-close-task
Source: https://github.com/attrigo/asapp/tree/main/.claude/skills/asapp-close-task
Command: npx skills add https://github.com/attrigo/asapp --skill asapp-close-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the final handoff for completed work by integrating a task branch into local main while preserving a clean, reversible Git state and keeping the plan file off main.

Core Features & Use Cases

  • End-to-end task closure: Handles the full close-out workflow for a finished branch, including spec status updates, squash merge preparation, and final verification.
  • Local-only Git integration: Keeps all actions on local branches so the work can be inspected, verified, or reverted before anything is shared.
  • Plan-aware release hygiene: Ensures the implementation lands on main while the planning document remains only on the task branch.
  • Use case: A developer has completed a TODO.md task, reviewed the changes, and wants to land the work cleanly into main without pushing or rewriting history.

Quick Start

Use this Skill to close the current finished task branch into local main and report the merge result, branch state, and verification status.

Frequently Asked Questions about asapp-close-task

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

FAQPage Schema
How do I safely squash merge a task branch into local main?

Squash merging a task branch into local main involves validating the branch, handling spec updates, performing the merge, and running verification checks to preserve a clean, reversible Git state.

How do I keep TODO.md implementation plans off the main branch in Git?

Keeping implementation plans off main requires plan-aware release hygiene during task closure, ensuring the TODO.md document remains only on the task branch while the actual code changes land on local main.

What is the best workflow for closing a finished Git task branch locally?

The best workflow for local task closure integrates the completed branch into main through squash merging, handles spec status updates, verifies the merge, and checks invariants before reporting completion, ensuring everything remains reversible.

Can I integrate a completed task branch into main without pushing to a remote repository?

Yes, you can integrate a completed task branch locally without pushing. The task closure workflow keeps all Git actions on local branches so the work can be inspected, verified, or reverted before anything is shared remotely.

Why does my Git branch merge fail invariant checks during task closure?

Invariant checks during task closure fail when local branch validation, spec update handling, or merge verification detects inconsistencies. The workflow requires all checks to pass before reporting completion to ensure a clean Git state.