session-wrap
Streamlines session wrap-up by automating documentation, analysis, and cleanup tasks.
Install
mkdir -p .claude/skills/session-wrap && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/6710" && unzip -o skill.zip -d .claude/skills/session-wrap && rm skill.zipInstalls to .claude/skills/session-wrap
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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.Key capabilities
- →Check git status
- →Extract key learnings
- →Suggest follow-up tasks
- →Automate documentation updates
How it works
Runs multiple analysis agents in parallel to validate changes, extract lessons, and format documentation.
Inputs & outputs
When to use session-wrap
- →Documenting work before committing
- →Cleaning up project context at the end of a shift
- →Extracting actionable learnings from a task
- →Preparing summaries for PR descriptions
About this skill
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.
When not to use it
- →If the session was purely read-only
- →When no changes have been made
Prerequisites
Limitations
- →Requires context of changes to be accurate
- →Parallel execution can be resource heavy
How it compares
It synthesizes multi-perspective analysis into structured documentation instead of raw chat logs.
Compared to similar skills
session-wrap side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| session-wrap (this skill) | 1 | 7mo | Review | Intermediate |
| task-handoff-checklist | 0 | 1mo | Review | Intermediate |
| workthrough | 10 | 8mo | Review | Beginner |
| doc-check | 4 | 2mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by team-attention
View all by team-attention →You might also like
task-handoff-checklist
inernoro
开发任务完成后自动扫描变更,从导航、文档、规则、工作流、测试、风险、代码质量、后续事项八个维度生成结构化交接报告,让验收者零追问即可核对。触发词:"交接"、"验收"、"handoff"、"/handoff"。
workthrough
bear2u
Automatically document all development work and code modifications in a structured workthrough format. Use this skill after completing any development task, bug fix, feature implementation, or code refactoring to create comprehensive documentation.
doc-check
coder
Checks if code changes require documentation updates
pr-draft-summary
openai
Create a PR title and draft description after substantive code changes are finished. Trigger when wrapping up a moderate-or-larger change (runtime code, tests, build config, docs with behavior impact) and you need the PR-ready summary block with change summary plus PR draft text.
create-pr-description
antinomyhq
Generate and create pull request descriptions automatically using GitHub CLI. Use when the user asks to create a PR, generate a PR description, make a pull request, or submit changes for review. Analyzes git diff and commit history to create comprehensive, meaningful PR descriptions that explain what changed, why it matters, and how to test it.
github-contributor
daymade
Strategic guide for becoming an effective GitHub contributor. Covers opportunity discovery, project selection, high-quality PR creation, and reputation building. Use when looking to contribute to open-source projects, building GitHub presence, or learning contribution best practices.