skills.rest
dimsour
dimsourCOMMUNITY
Explore all skills by this author →
GitHub

learn-from-fix

Convert resolved .NET bug fixes into classified lesson proposals.

2|Updated Apr 19, 2026
Search Tags:#bug fixing#institutional knowledge#Claude.md#lesson learning#Iron Law
One-click install
npx skills add https://github.com/dimsour/dotnet-ai-toolkit --skill learn-from-fix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: learn-from-fix
Source: https://github.com/dimsour/dotnet-ai-toolkit/tree/main/plugins/dotnet-copilot/skills/learn-from-fix
Command: npx skills add https://github.com/dimsour/dotnet-ai-toolkit --skill learn-from-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The 'learn-from-fix' skill helps you convert debugging wins into institutional knowledge, reducing the likelihood of recurring issues and promoting best practices.

Core Features & Use Cases

  • Bug Analysis: Summarize recent bug fixes in three sentences.
  • Lesson Classification: Classify the lesson as a Claude.md rule, an Iron Law, a Solution doc, or a reference update.
  • Artifact Drafting: Draft a proposal for the artifact, such as a rule text, a solution document, or an Iron Law.
  • User Confirmation: Request user confirmation before creating the artifact.
  • Integration: Triggered by the '/dotnet:work' command and followed by '/dotnet:learn-from-fix'.

Quick Start

After fixing a bug, run /dotnet:learn-from-fix to capture and document the lessons learned.

Frequently Asked Questions about learn-from-fix

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

FAQPage Schema
How do I document lessons learned from bug fixing to prevent recurring issues?▼

Bug fixing lesson documentation converts resolved defects into institutional knowledge, classifying them into rules or reference docs to prevent recurring issues. You summarize the fix, classify the lesson type, and draft a proposal artifact for confirmation.

What is the best way to capture institutional knowledge from a resolved .NET bug?▼

Institutional knowledge from a resolved .NET bug is captured by summarizing the fix in three sentences, classifying it as a Claude.md rule or Iron Law, and drafting an artifact. This structured approach ensures actionable lessons prevent future occurrences.

How do I create an Iron Law or Claude.md rule from a recent software bug fix?▼

An Iron Law or Claude.md rule from a software bug fix is created by summarizing the resolution, selecting the appropriate classification, and drafting the rule text. The system prompts you for classification and drafts a proposal for user confirmation before creation.

Can I use this bug lesson learning process across different .NET project types?▼

The bug lesson learning process is fully applicable across all .NET project types. It operates by summarizing the fix, classifying the lesson, and drafting an artifact regardless of the specific .NET framework or project template being used.

Do I need to manually classify bug fixing lessons, or is the process automated?▼

The bug fixing lesson process involves user input for classification, meaning it is not fully automated. The system summarizes the fix and prompts you to classify the lesson and confirm the drafted proposal artifact before adding it to your institutional knowledge.

Related Skills

Explore More Software Engineering Skills→
Ilenburg1993Ilenburg1993
3

reactive-bug-audit

Analyze stack traces and logs to identify root causes and apply minimal patches.

Community
Intermediate
GuitarAlchemistGuitarAlchemist

correct

Convert user corrections into permanent CLAUDE.md rules during AI sessions.

Official
Advanced
ImperialAutomationImperialAutomation
11

help-issues

Reference issue tracking commands and workflows for project coordination.

Official
Basic
koasis89koasis89

note

Create and manage notes using OMX persistent memory features.

Community
Basic