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

dotnet:learn-from-fix

Extract lessons from .NET bug fixes and draft rules or documentation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps developers extract valuable lessons from bug fixes, ensuring that future issues are prevented and institutional knowledge is built.

Core Features & Use Cases

  • Bug Analysis: Summarize what broke and why in a concise manner.
  • Lesson Classification: Categorize the lesson as a CLAUDE.md rule, Iron Law, Solution doc, or Reference update.
  • Artifact Drafting: Draft the artifact (rule text, solution doc, reference diff) for future reference.
  • Integration: Works seamlessly after a fix lands, guiding the user through the process of creating reusable rules and documentation.

Quick Start

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

Frequently Asked Questions about dotnet: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 fixes in .NET?▼

To document lessons learned from bug fixes, this Skill extracts the root cause and drafts reusable artifacts like Iron Laws, CLAUDE.md rules, or reference diffs to build institutional knowledge. It guides you through post-resolution analysis to prevent future issues.

What is the best way to create coding rules after resolving a software bug?▼

The best way to create coding rules after resolving a software bug is to run a post-fix analysis that classifies the lesson and drafts a formal rule. This Skill categorizes the fix as an Iron Law, solution doc, or reference update to institutionalize the knowledge.

Can I automatically generate solution documentation from a bug fix?▼

Yes, you can generate solution documentation from a bug fix by analyzing the resolved issue and drafting a structured document. This Skill summarizes what broke and why, then drafts the appropriate artifact for future reference within .NET environments.

How does bug analysis work for building institutional knowledge?▼

Bug analysis for building institutional knowledge works by summarizing the root cause of a failure and converting it into a categorized rule or document. This process captures the fix context and creates reusable references to prevent similar bugs.

When should I run a post-resolution bug analysis?▼

You should run a post-resolution bug analysis immediately after a fix lands and before moving to the next task. This ensures the context of what broke and why is fresh, allowing accurate drafting of rules and documentation to prevent future bugs.

Related Skills

Explore More Software Engineering Skills→
dimsourdimsour
2

dotnet:investigate

Automate .NET bug investigation with subagents for reproduction, root cause, impact, and fix strategy.

Community
Advanced
jaem1n207jaem1n207
18

eslint

Analyze JavaScript and TypeScript codebases with ESLint to enforce coding standards.

Community
Intermediate
actionbookactionbook
1.4k

coding-guidelines

Standardize Rust naming, formatting, and linting conventions across codebases.

Official
Basic
R2W1csR2W1cs
1

lint-and-validate

Lint and validate JavaScript and Python code for syntax and style issues.

Community
Intermediate