skills.rest
LeroyAdonis
LeroyAdonisCOMMUNITY
Explore all skills by this author →
GitHub

complete

Archives finished work specs, commits changes, and squash-merges branches to main.

Updated Mar 2, 2026
Search Tags:#git workflow#rollback#build plan#feature completion#squash merge#spec archiving#findings ledger
One-click install
npx skills add https://github.com/LeroyAdonis/kitfix-2.0 --skill complete-leroyadonis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: complete
Source: https://github.com/LeroyAdonis/kitfix-2.0/tree/main/.agents/skills/complete
Command: npx skills add https://github.com/LeroyAdonis/kitfix-2.0 --skill complete-leroyadonis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Closing out a finished feature, fix, or rollback involves many error-prone manual steps: verifying the work, archiving the spec, updating the build plan, committing, merging, and pushing. This Skill standardizes that entire closeout workflow so nothing is skipped and project history stays clean. ## Core Features & Use Cases - Final Safety Pass: Blocks merging unless verification commands pass, behavioral done-whens have evidence, and no open P0/P1 findings remain in the findings ledger. - Structured Archiving: Moves the completed spec into blueprint/history/features/, fixes/, or rollbacks/, updates the build plan, and archives resolved findings with globally unique IDs. - Controlled Git Workflow: Creates one conventional work commit, squash-merges the branch to main only with explicit approval, and asks separately before pushing. - Use Case: After /implement finishes building a feature and all checks pass, run /complete to log the work, merge the branch cleanly, and reset the workspace for the next task. ## Quick Start Ask the assistant to run /complete to finish, verify, archive, and merge the current feature branch after it has been built and reviewed.

Frequently Asked Questions about complete

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

FAQPage Schema
How do I merge a finished feature branch to main safely?▼

Run the complete skill after the work is built and reviewed. It performs a final safety pass, archives the spec, makes one conventional work commit, then squash-merges the branch to main only after your explicit approval.

What happens if verification tests fail before merging?▼

The merge is blocked. The documented Verify command, or the fallback build and tests, must pass first, and behavioral done-whens need evidence from a check run against the running app before the skill proceeds.

Can I merge with open code review findings?▼

No. Any P0 or P1 finding marked open or fixed in the findings ledger blocks the merge. The only exceptions are findings explicitly marked accepted by the user with a recorded reason, or invalid after re-examination.

Does the skill push to the remote repository automatically?▼

No. Merging and pushing are separate decisions. After an approved merge, the skill stops and asks whether to push main, and only pushes after a separate explicit yes in the current chat.

How are rollbacks handled differently from features?▼

Rollbacks archive to blueprint/history/rollbacks/ with a dated filename, preserve the original feature archive, uncheck the target item in the build plan, and append a rollback note with the date and archive path.

Related Skills

Explore More Software Engineering Skills→
dlt-hubdlt-hub
5.7k

worktree-from-issue

Create a git worktree and per-issue branch for a GitHub issue.

Official
Advanced
benjaminfauchaldbenjaminfauchald

ship

Automates GitHub PRs, CI checks, and deploys across branches to production.

Community
Intermediate
swyxioswyxio
154

autoreview

Run structured closeout code reviews on branches, PRs, and commits.

Community
Advanced
Jia-Hong-PengJia-Hong-Peng

land-and-deploy

Merges pull requests and verifies production canary health after CI/CD deployment completes.

Community
Advanced