← ClaudeAtlas

reflectlisted

Capture session knowledge (gotchas, patterns, integration quirks) into the project's knowledge base. Use when: session involved tricky bugs, new integrations, non-obvious patterns, or hard-won lessons. Also use when asked to "reflect", "capture lessons", "what did we learn", "session recap", or "save knowledge". Works after any coding session, not just commits.
nsollazzo/skills · ★ 0 · Code & Development · score 75
Install: claude install-skill nsollazzo/skills
# Reflect — Session Knowledge Capture Scan the current session for valuable lessons and route them to the right knowledge target. ## Workflow ### Step 1: Gather Session Context Read-only scan of what happened this session: ```bash git diff main --stat git log main..HEAD --oneline git diff main ``` Also review conversation context: problems solved, errors hit, workarounds applied, patterns discovered. ### Step 2: Scan Existing Knowledge Base Quick skim (not full read) to avoid duplicates: - `~/.claude/projects/*/memory/MEMORY.md` — current gotchas - Project `CLAUDE.md` — current rules - `~/.claude/skills/` directory listing — skill coverage - `docs/` directory listing — existing documentation ### Step 3: Identify Knowledge Gaps Classify each insight into exactly one category: | Category | Target | When | |----------|--------|------| | **Gotcha** | MEMORY.md | Non-obvious trap or workaround | | **Rule** | CLAUDE.md | Project-wide always/never pattern | | **Skill update** | `.claude/skills/<name>/` | Existing skill missing info | | **New skill** | `/skill-creator` | New integration worth codifying | | **Docs** | `docs/` | Missing guide or troubleshooting | **Filters:** - Skip routine changes (simple renames, formatting, obvious fixes) - Skip duplicates of existing knowledge - Max 7 suggestions - Priority: gotchas > rules > skill updates > docs > new skills ### Step 4: Present Summary Concise table — scannable in 5 seconds: ```markdown ## Session Reflection | # |