Wrap Up

Session Wrap-Up

The single learning engine for the skill system. Mirrors how learning works in nature:

Experience (work) → Awareness (learning notes) → Consolidation (wrap-up)

Usage

/wrap-up {session title}

Arguments

• $0 - Session title describing the main work done (e.g., "API Auth Refactor")

---

Step 1: Gather All File Changes

CRITICAL: Before anything else, run git commands to capture ALL changes. In long sessions, memory alone will miss things.

git status
git diff HEAD
git ls-files --others --exclude-standard

From the output, build a comprehensive list of:

• All modified files and what changed
• All new files created
• All deleted files
• Nature of changes (bug fix, feature, refactor, etc.)

DO NOT proceed to Step 2 until git output is reviewed.

---

Step 2: Create Journey

Using file changes from Step 1 AND conversation context, create a journey at .claude/journeys/{date}-{slug}.md.

Include:

• Summary: What was accomplished and why it matters
• What Was Done: Numbered list of major items
• Key Learnings: Insights that prevent future mistakes
• Files Changed: Table of files and changes
• Patterns Discovered: Code examples of reusable patterns
• Decisions Made: Table of decisions and rationale

---

Step 3: Process Learning Notes

Search ALL skill files for inline learning notes left during the session:

# Find all learning notes across skills
grep -r "` comment gets replaced by the integrated content
4. **Update the `updated` date** in the skill's frontmatter

### Learning Note Format (for reference)

During work, learning notes are left inline:
```markdown
### Some Section
Existing instruction text...

After consolidation, the section reads naturally with the learning absorbed:

### Some Section
Existing instruction text. Note: X needs Y because Z.

---

Step 4: Evolve Skills from Journey

Read all skills from .claude/skills/*/SKILL.md and compare against journey learnings.

For each skill, check:

• Does the journey contain patterns the skill should document?
• Were there edge cases or gotchas the skill should warn about?
• Are there new verification checklist items?
• Did we discover something that contradicts current skill instructions?

For each skill that needs updates:

1. Read current SKILL.md
2. Apply changes based on learnings
3. Update the updated date in frontmatter

---

Step 5: Cross-Pollinate Shared Patterns

Check if any learnings from the session apply across multiple skills.

1. Read .claude/skills/_patterns.md (create it if it doesn't exist yet)
2. If a learning is cross-cutting (applies to multiple skills or domains), add it to _patterns.md
3. If a pattern in _patterns.md is outdated based on session work, update it

Examples of cross-cutting learnings:

• A new error handling pattern discovered while building an API endpoint → add to shared patterns
• A database query optimization found during feature work → add to shared patterns
• A validation pattern discovered in form handling → add to shared patterns

---

Step 6: Prune Stale Content

Review skills touched during the session. Look for:

• Sections documenting patterns for deprecated/removed features
• Duplicate content that now lives in _patterns.md
• Instructions that conflict with current codebase reality

If something looks stale, remove it. Keep skills lean — context window space is valuable.

---

Step 7: Update Journey with Evolutions

Add a section to the journey documenting skill changes:

## Skills Evolved

| Skill | Changes |
|-------|---------|
| skill-name | Added error handling pattern |
| _patterns | Updated validation rules |

---

Skill Evolution Guidelines

| Session Content | Action | |-----------------|--------| | New component/module pattern | Add to relevant skill's patterns section | | Bug fix with root cause | Add to gotchas/checklist in relevant skill | | New feature implemented | Update feature documentation in relevant skill | | Cross-cutting pattern | Update _patterns.md | | New convention discovered | Update _patterns.md |

---

Example Output

Session: API Auth Refactor

1. Gathered file changes (8 modified, 2 created)
2. Created journey: .claude/journeys/2026-02-08-api-auth-refactor.md
3. Processed 2 learning notes:
   - auth-flow: integrated token refresh edge case
   - api-client: integrated retry pattern
4. Evolved 2 skills from journey learnings:
   - auth-flow: added session expiry handling
   - api-client: added graceful degradation
5. Cross-pollinated: added error retry pattern to _patterns.md
6. Pruned: removed outdated middleware example from api-client
7. Updated journey with evolution summary

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: MeshJS
• Source: MeshJS/evolving-claude-skills
• License: Apache-2.0

Install and usage instructions live in the source repository linked above.