Capture end-of-session lessons as searchable trivia memories with rationale.
npx skills add https://github.com/ceejbot/ceej-skills --skill session-retro-ceejbot
Please help me install this Agent Skill. Skill: session-retro Source: https://github.com/ceejbot/ceej-skills/tree/main/skills/session-retro Command: npx skills add https://github.com/ceejbot/ceej-skills --skill session-retro-ceejbot
It helps you capture what you learned in a project session so the insight is reused next time instead of being forgotten after the work ends.
current-focus for ongoing state rather than incorrectly treating it as a durable retro lesson.Use session-retro when you say “let’s wrap up” or “let’s retro” after meaningful progress and the skill will store 0–2 durable lessons tagged to your project.
High-intent search queries and answers about installing and using this skill.
Run a session retro after meaningful work concludes to capture durable lessons. The skill summarizes outcomes from features or bug fixes into searchable trivia memories, requiring specific worked or avoided entries with rationale before a final commit.
Retaining project knowledge requires writing session retrospectives that separate ongoing state from durable lessons. This approach stores zero to two generalized insights per session as searchable mnemonics, ensuring past mistakes are recalled and avoided in future work.
Skip the retrospective for trivial or purely exploratory sessions. Retrospectives should only be applied after meaningful work where outcomes can be summarized, such as when a feature lands, a bug gets fixed, or an investigation concludes.
Separate current project focus from durable lessons by updating the current focus as state rather than treating it as a retro lesson. The skill mandates this separation so ongoing status is not incorrectly stored as a permanent mnemonic.
You can recall prior retro memories and rate what helped versus what was noise. This feedback loop retrieves existing project trivia memories, allowing you to evaluate past lessons and continuously improve your project workflow.
Providing a rationale for what worked or didn't work is mandatory during a retro. The skill requires a non-negotiable why for each entry so that specific lessons generalize into durable knowledge for future code reviews.
anyekoutoumingAnalyzes sessions to identify actionable improvements for prompts, workflows, and templates.
jonkikyConsolidate and retrieve project learnings across sessions.
PalbahngmiyineExecute a four-phase end-of-session wrap-up with Korean Conventional Commits.
wilsonfaustinoAutomate end-of-session knowledge capture with Obsidian notes and memory updates.