session-wrap▌
ai-native-camp/camp-2 · updated Apr 8, 2026
Comprehensive session wrap-up workflow with multi-agent analysis.
Session Wrap Skill
Comprehensive session wrap-up workflow with multi-agent analysis.
Execution Flow
┌─────────────────────────────────────────────────────┐
│ 1. Check Git Status │
├─────────────────────────────────────────────────────┤
│ 2. Phase 1: 4 Analysis Agents (Parallel) │
│ ┌─────────────────┬─────────────────┐ │
│ │ doc-updater │ automation- │ │
│ │ (docs update) │ scout │ │
│ ├─────────────────┼─────────────────┤ │
│ │ learning- │ followup- │ │
│ │ extractor │ suggester │ │
│ └─────────────────┴─────────────────┘ │
├─────────────────────────────────────────────────────┤
│ 3. Phase 2: Validation Agent (Sequential) │
│ ┌───────────────────────────────────┐ │
│ │ duplicate-checker │ │
│ │ (Validate Phase 1 proposals) │ │
│ └───────────────────────────────────┘ │
├─────────────────────────────────────────────────────┤
│ 4. Integrate Results & AskUserQuestion │
├─────────────────────────────────────────────────────┤
│ 5. Execute Selected Actions │
└─────────────────────────────────────────────────────┘
Step 1: Check Git Status
git status --short
git diff --stat HEAD~3 2>/dev/null || git diff --stat
Step 2: Phase 1 - Analysis Agents (Parallel)
Execute 4 agents in parallel (single message with 4 Task calls).
Session Summary (Provide to all agents)
Session Summary:
- Work: [Main tasks performed in session]
- Files: [Created/modified files]
- Decisions: [Key decisions made]
Parallel Execution
Task(
subagent_type="doc-updater",
description="Document update analysis",
prompt="[Session Summary]\n\nAnalyze if CLAUDE.md, context.md need updates."
)
Task(
subagent_type="automation-scout",
description="Automation pattern analysis",
prompt="[Session Summary]\n\nAnalyze repetitive patterns or automation opportunities."
)
Task(
subagent_type="learning-extractor",
description="Learning points extraction",
prompt="[Session Summary]\n\nExtract learnings, mistakes, and new discoveries."
)
Task(
subagent_type="followup-suggester",
description="Follow-up task suggestions",
prompt="[Session Summary]\n\nSuggest incomplete tasks and next session priorities."
)
Agent Roles
| Agent | Role | Output |
|---|---|---|
| doc-updater | Analyze CLAUDE.md/context.md updates | Specific content to add |
| automation-scout | Detect automation patterns | skill/command/agent suggestions |
| learning-extractor | Extract learning points | TIL format summary |
| followup-suggester | Suggest follow-up tasks | Prioritized task list |
Step 3: Phase 2 - Validation Agent (Sequential)
Run after Phase 1 completes (dependency on Phase 1 results).
Task(
subagent_type="duplicate-checker",
description="Phase 1 proposal validation",
prompt="""
Validate Phase 1 analysis results.
## doc-updater proposals:
[doc-updater results]
## automation-scout proposals:
[automation-scout results]
Check if proposals duplicate existing docs/automation:
1. Complete duplicate: Recommend skip
2. Partial duplicate: Suggest merge approach
3. No duplicate: Approve for addition
"""
)
Step 4: Integrate Results
## Wrap Analysis Results
### Documentation Updates
[doc-updater summary]
- Duplicate check: [duplicate-checker feedback]
### Automation Suggestions
[automation-scout summary]
- Duplicate check: [duplicate-checker feedback]
### Learning Points
[learning-extractor summary]
### Follow-up Tasks
[followup-suggester summary]
Step 5: Action Selection
AskUserQuestion(
questions=[{
"question": "Which actions would you like to perform?",
"header": "Wrap Options",
"multiSelect": true,
"options": [
{"label": "Create commit (Recommended)", "description": "Commit changes"},
{"label": "Update CLAUDE.md", "description": "Document new knowledge/workflows"},
{"label": "Create automation", "description": "Generate skill/command/agent"},
{"label": "Skip", "description": "End without action"}
]
}]
)
Step 6: Execute Selected Actions
Execute only the actions selected by user.
Quick Reference
When to Use
- End of significant work session
- Before switching to different project
- After completing a feature or fixing a bug
When to Skip
- Very short session with trivial changes
- Only reading/exploring code
- Quick one-off question answered
Arguments
- Empty: Proceed interactively (full workflow)
- Message provided: Use as commit message and commit directly
Additional Resources
See references/multi-agent-patterns.md for detailed orchestration patterns.
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★34 reviews- ★★★★★Zaid Mehta· Dec 16, 2024
We added session-wrap from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Chinedu Martinez· Dec 4, 2024
Useful defaults in session-wrap — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Hassan Wang· Nov 23, 2024
I recommend session-wrap for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Ira Brown· Nov 7, 2024
Keeps context tight: session-wrap is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Ishan Tandon· Oct 26, 2024
session-wrap has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Benjamin Taylor· Oct 14, 2024
session-wrap reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Hassan Abbas· Sep 25, 2024
I recommend session-wrap for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Oshnikdeep· Sep 21, 2024
Keeps context tight: session-wrap is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Piyush G· Sep 17, 2024
session-wrap fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Hassan Li· Aug 16, 2024
session-wrap reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 34