Magnus Hedemarkandfactory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
c0c7690724
Move the 8 directories under bundles/ to the repo root via git mv and remove the now-empty bundles/ directory. Replace the "bundles" entry in pyproject.toml [tool.deptry] extend_exclude with the 8 moved dir names so the moved trees stay excluded from Python dependency analysis. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
2.1 KiB
name, description, license, compatibility, metadata
| name | description | license | compatibility | metadata | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| session-wrap | Use when the user is wrapping up a session — summarizing decisions, filing follow-up issues, saving state, or committing work. Keywords: wrap, done, finish, save, close, ship, summarize. | MIT | Compatible with any agent supporting the Agent Skills format |
|
Session Wrap
This skill is part of the developer-triage bundle, generated by workflow-architect on 2026-05-29.
When to Use
Activate when the user signals session completion or starts summarizing what happened. This usually fires based on explicit wrap language ("let's wrap up," "I'm done for now") or session duration signals.
What to Do
-
Summarize what was accomplished. List the key outcomes of the session: what was built, fixed, decided, or learned. Be specific — reference PRs filed, bugs fixed, issues created.
-
Capture incomplete items. Note anything that was started but not finished. Save the state so the next session can pick up where this one left off.
-
File follow-ups. If any decisions need tracking, file issues or tasks. If any questions remain open, note them.
-
Save session state. Commit or stash any work-in-progress. Write a session note if the user's workflow includes that step.
-
Offer the exit. Ask if there's anything else before signing off.
Transition Signals
The session ends after the user confirms the wrap summary or says they're done. No further transitions — this is the terminal phase.
What to Tell the User
Start with the positive (what got done), then cover what's left. Keep it brief — the user is mentally checking out. End with a clear statement of where things stand for next time.
Example:
"This session's summary:
✅ PR #142 reviewed and approved
✅ Rate limiter feature branch created (+127 lines)
❌ Thought about but didn't start: the cache invalidation issue
(#89 — still needs investigation)
I've stashed the WIP branch. Next session: pick up cache invalidation
or tackle whatever's new. Sound good?"