wrap-up

Posts a condensed wrap-up comment to the ticket and marks it completed.

15|1|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/fprochazka/claude-code-plugins --skill wrap-up-fprochazka
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wrap-up
Source: https://github.com/fprochazka/claude-code-plugins/tree/main/plugins/sdlc/skills/wrap-up
Command: npx skills add https://github.com/fprochazka/claude-code-plugins --skill wrap-up-fprochazka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Closing out finished work often means manually gathering session results, attaching documents, and writing a ticket summary — a repetitive step that loses verification numbers and findings when done hastily. ## Core Features & Use Cases - Document Attachment: Invokes the ticket-attach-docs command first so produced documents land on the ticket regardless of what happens next. - Dense Wrap-Up Comments: Drafts structured comments (outcome, verification, findings, limits, follow-ups) from the session itself, with a ~50-line ceiling and no padding. - Ticket Closure: Reads the tracker's real workflow states and marks the ticket completed without touching assignee, labels, or priority. - Use Case: After merging an MR and verifying production metrics in a session, run the wrap-up to attach the plan documents, post a comment with the exact verification numbers observed, and close the ticket. ## Quick Start Run the wrap-up skill to attach this session's documents to the ticket, post a wrap-up comment with the verification results, and mark the ticket completed.

Frequently Asked Questions about wrap-up

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

FAQPage Schema
How do I write a wrap-up comment when closing a ticket?▼

Draft the comment from the session itself with optional sections: outcome, verification with exact numbers and sources, findings, limits, and follow-ups. Keep it under roughly 50 lines, use bare lists, and never restate the ticket or diff.

How to attach documents to a ticket before closing it?▼

Invoke the ticket-attach-docs command before posting any comment or changing state. It runs first because later steps can stall, and the documents belong on the ticket regardless of whether it gets closed.

Can the wrap-up comment include numbers I did not measure in the session?▼

No. Only report figures exactly as measured during the session. If a number cannot be stated precisely, drop it or state the reading you actually have, and never re-run checks or queries to fill gaps.

When should a wrap-up be split into multiple comments?▼

Split when one comment would bury its best parts, such as a long production verification or follow-ups deserving their own thread. Split along section boundaries, and each comment must stand alone and obey the density rules.

What happens if the session never confirmed the work is finished?▼

Treat the state as unknown, keep it out of the comment, and mention it to the user. Post the comment anyway, but ask the user before marking the ticket completed.