reflexion

Capture significant errors and root causes into structured reflexion records.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/gudzenkov/SuperClaudeZero --skill reflexion-gudzenkov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reflexion
Source: https://github.com/gudzenkov/SuperClaudeZero/tree/main/.claude/skills/reflexion
Command: npx skills add https://github.com/gudzenkov/SuperClaudeZero --skill reflexion-gudzenkov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture significant errors, root causes, and prevention strategies for future reference, turning hard-won insights into reusable knowledge.

Core Features & Use Cases

  • Structured reflexion records are stored in Serena project memory under the reflexion namespace.
  • Provides a repeatable 5-part analysis: Known Issue, Symptoms, Root Cause, Solution, Prevention.
  • Enables pattern matching and learning across projects.

Quick Start

Create a reflexion entry for a recent debugging session to begin capturing insights.

Frequently Asked Questions about reflexion

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

FAQPage Schema
How do I document root-cause analysis for debugging sessions?

To document root-cause analysis, capture the known issue, symptoms, root cause, solution, and prevention in a structured reflexion record stored in project memory. This creates consistent knowledge-base entries for future reference.

What is the best way to structure a postmortem for software errors?

The best way to structure a postmortem is using a 5-part analysis format: Known Issue, Symptoms, Root Cause, Solution, and Prevention. This is supplemented by metadata fields like date, severity, and tags.

How do I store error analysis insights for future development projects?

You store error analysis insights by creating reflexion records under a dedicated namespace in Serena project memory. This enables pattern matching and learning across multiple development projects.

Can I use reflexion records to build a knowledge base from past mistakes?

Yes, you can use reflexion records to build a knowledge base. They capture significant errors and their prevention strategies, turning hard-won debugging insights into reusable knowledge for future reference.

What metadata should I include when logging a postmortem entry?

When logging a postmortem entry, include metadata fields for date, session_id, agent, task, severity, and tags in the reflexion frontmatter. This metadata categorizes the markdown body for future pattern matching.

When should I not use a structured reflexion record for error tracking?

You should avoid using a structured reflexion record for trivial errors that lack significant root causes or prevention strategies. It is designed for capturing meaningful, hard-won insights from complex debugging sessions.