learn-mistake

Record Claude's mistakes as Historical Incidents in REPO_MAP.md.

2|1|Updated Dec 15, 2025
One-click install
npx skills add https://github.com/sgpropertyanalytics/sg-property-analytics --skill learn-mistake
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learn-mistake
Source: https://github.com/sgpropertyanalytics/sg-property-analytics/tree/main/.claude/skills/learn-mistake
Command: npx skills add https://github.com/sgpropertyanalytics/sg-property-analytics --skill learn-mistake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Records Claude's mistakes as Historical Incidents in REPO_MAP.md to prevent repeating harmful recommendations and to preserve institutional memory for future reviews.

Core Features & Use Cases

  • Incident formatting: Uses a standardized template (What happened, Impact, Why it was wrong, Fix, Lesson) for consistency.
  • Append to REPO_MAP.md: Adds new incidents under the Historical Incidents section to improve traceability.
  • Risk-awareness updates: Optionally updates risk-agent awareness and CLAUDE.md references with lessons learned.
  • Guided workflow: Step-by-step process from gathering information to confirming updates.

Quick Start

Append a clearly formatted incident to REPO_MAP.md to capture the lesson for future reference.

Frequently Asked Questions about learn-mistake

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

FAQPage Schema
How do I record Claude's mistakes to prevent repeating bad recommendations?

You record Claude mistakes by appending structured incidents to REPO_MAP.md. This creates a persistent historical memory capturing what happened, the impact, why it was wrong, the fix, and the lesson learned to prevent repeating harmful recommendations.

What is the standardized format for documenting an incident in historical memory?

The standardized incident format for historical memory includes five fields: What happened, Impact, Why it was wrong, Fix, and Lesson. This structure ensures consistency when appending incidents to REPO_MAP.md for future reviews.

How do I capture production issues caused by AI recommendations in my documentation?

You capture production issues by appending them to REPO_MAP.md under the Historical Incidents section. This applies to any scenario where an AI recommendation leads to a bug or production issue, enabling structured incident capture for future reference.

Can I update risk management guardrails automatically after documenting a mistake?

Yes, after documenting a mistake in REPO_MAP.md, you can optionally update risk-agent awareness and CLAUDE.md references with lessons learned. This ensures risk management guardrails reflect the newly captured incident data.

When should I use a structured incident capture process for AI mistakes?

You should use structured incident capture whenever a recommendation leads to a bug, production issue, or misalignment with documented practices. It preserves institutional memory and improves traceability for future risk management reviews.