reflect

Captures session lessons into memory files, project instructions, skills, and docs.

Updated Jun 15, 2026
One-click install
npx skills add https://github.com/nsollazzo/ship-kit --skill reflect-nsollazzo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reflect
Source: https://github.com/nsollazzo/ship-kit/tree/main/.agents/skills/reflect
Command: npx skills add https://github.com/nsollazzo/ship-kit --skill reflect-nsollazzo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Hard-won lessons from a coding session — tricky bugs, integration quirks, non-obvious patterns — are usually lost when the session ends. This Skill scans the session, identifies knowledge gaps, and routes each insight to the right knowledge target so the team never re-learns the same lesson. ## Core Features & Use Cases - Session Knowledge Scan: Reviews git diffs, commit history, and conversation context to surface gotchas, rules, and patterns worth saving. - Classified Routing: Sorts each insight into exactly one target — memory/MEMORY.md for gotchas, the project instruction file for rules, skill folders for skill updates, or docs/ for missing guides. - Approval-Gated Writes: Presents a verdict table with save/skip recommendations and never writes anything without an explicit plain-chat approval from the user. - Use Case: After debugging a runtime panic caused by nested array validators, run reflect to capture the gotcha into MEMORY.md and update the relevant skill, so the next session avoids the same trap. ## Quick Start Ask the agent to reflect on this session and capture what we learned into the knowledge base.

Frequently Asked Questions about reflect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture lessons learned from a coding session?▼

Run the reflect workflow after your session. It scans git diffs, commit history, and conversation context, classifies insights as gotchas, rules, skill updates, or docs, and presents a verdict table for your approval before writing anything.

What is the difference between reflect and a session wrap-up?▼

Reflect writes approved knowledge into the knowledge base (memory, instruction files, skills, docs), while wrap-up only reports unfinished work and writes nothing. Use reflect to persist lessons and wrap-up to summarize outstanding tasks.

Does reflect modify files without my approval?▼

No. Reflect never auto-applies changes. It presents a verdict table and waits for a plain chat reply — ok, no, or a comment adjusting the verdicts — before editing any knowledge files.

Can reflect create new skills automatically?▼

No. When it identifies a gap worth a new skill, it only prints a recommendation to build that skill with your skill-creation flow. It never creates skills directly and never modifies source code.

When should I not use session knowledge capture?▼

Skip it for routine sessions involving simple renames, formatting, or obvious fixes, since reflect filters these out anyway. It is designed for sessions with tricky bugs, new integrations, or non-obvious patterns worth persisting.