session-wrap
This skill should be used when the user asks to "wrap up session", "end session", "session wrap", "/wrap", "document learnings", "what should I commit", or wants to analyze completed work before ending a coding session.
How do I install this agent skill?
npx skills add https://github.com/ai-native-camp/camp-2 --skill session-wrapIs this agent skill safe to install?
- Gen Agent Trust Hubwarn
The 'session-wrap' skill automates end-of-session tasks by analyzing workspace changes to suggest documentation updates, learning points, and new automations. It utilizes a multi-agent orchestration pattern for parallel analysis. Security considerations include the generation of executable scripts based on session content and a susceptibility to indirect prompt injection from workspace files.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
- Runlayerpass
2 files scanned · No issues
- ZeroLeakspass
Score: 93/100 · 2 sections analyzed
What does this agent skill do?
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.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/ai-native-camp/camp-2/session-wrap">View session-wrap on skillZs</a>