wrap
Session wrap-up workflow. Use when user asks to "wrap up session", "end session", "/wrap", or wants to analyze completed work before ending.
What this skill does
# 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 │ │
│ └───────────────────────────────────┘ │
├─────────────────────────────────────────────────────┤
│ 4. Integrate Results & AskUserQuestion │
├─────────────────────────────────────────────────────┤
│ 5. Execute Selected Actions │
└─────────────────────────────────────────────────────┘
```
## Step 1: Check Git Status
```bash
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]
- Files: [Created/modified files]
- Decisions: [Key decisions made]
```
### Parallel Execution
```
Task(subagent_type="doc-updater", ...)
Task(subagent_type="automation-scout", ...)
Task(subagent_type="learning-extractor", ...)
Task(subagent_type="followup-suggester", ...)
```
| Agent | Role | Output |
|-------|------|--------|
| **doc-updater** | 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
Run after Phase 1 completes.
```
Task(
subagent_type="duplicate-checker",
prompt="""
Validate Phase 1 results.
## doc-updater proposals:
[doc-updater results]
## automation-scout proposals:
[automation-scout results]
"""
)
```
## Step 4: Integrate Results
```markdown
## 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"},
{"label": "Create automation", "description": "Generate skill/command/agent"},
{"label": "Skip", "description": "End without action"}
]
}]
)
```
## Step 6: Execute Selected Actions
Execute only user-selected actions.
---
## 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 directly
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.