reflect

Analyze session transcripts or git history to extract actionable insights and friction points.

2|Updated Jul 11, 2024
One-click install
npx skills add https://github.com/nicograef/handbook --skill reflect-nicograef
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reflect
Source: https://github.com/nicograef/handbook/tree/main/.claude/skills/reflect
Command: npx skills add https://github.com/nicograef/handbook --skill reflect-nicograef

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of knowledge evaporation by providing a structured way to capture insights, friction, and solutions from work sessions before they are forgotten.

Core Features & Use Cases

  • Session Analysis: Automatically synthesizes problems, solutions, and insights from current or past session transcripts.
  • Git-based Reflection: Derives learnings from commit history when session transcripts are unavailable.
  • Improvement Planning: Categorizes learnings into memory, rules, skills, documentation, or tooling, and ensures they are integrated into the project's existing artifacts.

Quick Start

Run the reflect skill to analyze the last three sessions and generate an improvement plan.

Frequently Asked Questions about reflect

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

FAQPage Schema
How do I run a structured retrospective to extract insights from my development sessions?

Structured retrospectives analyze session transcripts or git history to extract actionable insights and friction points. They synthesize findings into categorized project updates across memory, rules, skills, documentation, or tooling.

Can I generate continuous improvement plans from git commit history?

Continuous improvement plans can be derived directly from git commit history when session transcripts are unavailable. The reflection process analyzes commit logs to identify friction points and categorize learnings into project artifacts.

What is the best way to prevent knowledge evaporation after a coding session?

Preventing knowledge evaporation requires capturing insights, friction, and solutions from work sessions before they are forgotten. Structured session analysis automatically synthesizes problems and solutions into categorized improvement plans.

How do I categorize session learnings into project documentation and memory?

Session learnings are categorized into memory, rules, skills, documentation, or tooling during the reflection process. This ensures insights are integrated into the project's existing artifacts across project-specific memory directories.

Does the retrospective analysis work without explicit session transcripts?

Retrospective analysis works without explicit session transcripts by falling back to git-based reflection. It derives learnings from commit history to synthesize findings and generate actionable improvement plans.

What limitations exist when analyzing session logs for workflow optimization?

Workflow optimization through session analysis requires integration with local session logs and git history. Without these data sources, the ability to synthesize findings and derive friction points is constrained.