wrap-up

Creates tickets, posts insights, and generates devlogs for deferred session work.

1|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/williamthorsen/codeassembly --skill wrap-up-williamthorsen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrap-up
Source: https://github.com/williamthorsen/codeassembly/tree/main/packages/agents/content/skills/wrap-up
Command: npx skills add https://github.com/williamthorsen/codeassembly --skill wrap-up-williamthorsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? At the end of a coding session, deferred findings, legacy issues, and insights are easily lost. This Skill inventories everything left unaddressed and turns it into tracked tickets, ticket comments, and devlog artifacts after user confirmation. ## Core Features & Use Cases - Session assessment: Detects the session type (orchestrated, interactive dev, review, or research) and scans run-summaries, review artifacts, and conversation for deferred items and insights. - Classified inventory with action menu: Presents findings using an F/W/T/R/S prefix vocabulary with complexity levels, offers drive-by fixes for trivial items, and lets the user batch or individually ticket the rest. - Persistent deferred-findings record: Writes a deferred-findings artifact cross-referencing created tickets and dropped items so nothing disappears silently. - Use Case: After an orchestrated code run, invoke wrap-up to convert unresolved review findings into GitHub tickets, post insights as ticket comments, and save a session devlog linked to the run ID. ## Quick Start Ask the agent to wrap up the session and create tickets for any deferred findings.

Frequently Asked Questions about wrap-up

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

FAQPage Schema
How do I create tickets for deferred findings after a coding session?

Invoke the wrap-up skill at session end. It scans run-summaries, review artifacts, and conversation for deferred items, presents a numbered action menu, and creates GitHub tickets via the create-ticket skill only after you confirm.

How does wrap-up classify findings and insights?

Findings use an F/W/T/R/S prefix vocabulary (fixme, warning, todo, recommendation, suggestion) with a legacy suffix for pre-existing issues, plus I-prefixed insights. Each finding also gets a complexity level from 1 to 4 to decide drive-by versus ticket handling.

What are drive-by fixes in the wrap-up workflow?

Drive-by fixes are trivial findings (complexity levels 1-2) that the agent can apply immediately on the current branch. They are offered before the main menu, subject to branch-size and code-overlap guardrails, and skipped items return to the findings pool.

Does wrap-up execute actions automatically without confirmation?

No. Wrap-up always waits for the user to respond to the action menu before executing anything. Unselected findings are implicitly dropped but still recorded in the deferred-findings artifact's Dropped section.

Where does wrap-up save the deferred-findings record?

It writes a timestamped deferred-findings markdown artifact under the ticket directory when a ticket ID exists, or under a project-level deferred-findings directory otherwise. The artifact cross-references created tickets and dropped items.