skills.rest
emanuelrechsteiner
emanuelrechsteinerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pattern-document

Extract learnings from bug fixes and anti-patterns into .claude/rules documents.

Updated Aug 23, 2026
Search Tags:#documentation#anti-pattern#bug-fix#learning-extraction#pattern-document#rule-documentation
One-click install
npx skills add https://github.com/emanuelrechsteiner/FairSplit --skill pattern-document
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pattern-document
Source: https://github.com/emanuelrechsteiner/FairSplit/tree/main/.claude/skills/pattern-document
Command: npx skills add https://github.com/emanuelrechsteiner/FairSplit --skill pattern-document

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Pattern-document helps teams capture reusable learnings from bugs, fixes, and discovered anti-patterns, and turn them into formal rule documents under .claude/rules for future reference.

Core Features & Use Cases

  • Extract learnings from bug fixes, successful implementations, or discovered anti-patterns.
  • Create structured rule documents in .claude/rules/ to codify patterns for teams.
  • Use Case: after a tricky bug or a design decision to capture the pattern and prevent recurrence.

Quick Start

Run the pattern-document workflow to extract a learning from your latest bug fix and generate a new rule document.

Frequently Asked Questions about pattern-document

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

FAQPage Schema
How do I extract learnings from bug fixes and create reusable rule documents?▼

You can extract learnings from bug fixes by running the pattern-document workflow, which analyzes the fix and generates structured rule documents in .claude/rules to prevent recurrence across projects.

When should I generate documentation for discovered anti-patterns?▼

You should generate documentation immediately after discovering bugs, implementing successful solutions, or identifying anti-patterns, ensuring the learning is captured with full context before details are forgotten.

Does this pattern extraction workflow require any external dependencies?▼

No external dependencies are required. The pattern-document workflow uses only a references component to analyze your code and generate rule documents, operating independently within your existing environment.

What is the best way to document code patterns for team reuse?▼

The best way to document code patterns is to codify them as structured rule documents under .claude/rules, applying a consistent naming convention and linking to templates so team members can automatically ingest and apply them.

Can I use rule documents generated from bug fixes across multiple projects?▼

Yes, rule documents generated from bug fixes are designed for reuse across projects. The pattern-document workflow produces structured content with discovery context and automated ingestion naming conventions for broad application.

Why should I codify anti-patterns into .claude/rules instead of standard documentation?▼

Codifying anti-patterns into .claude/rules transforms static notes into automated, reusable rules with structured context and naming conventions, preventing recurrence more effectively than standard documentation.

Related Skills

Explore More Software Engineering Skills→
jasonwilmotjasonwilmot

scan-similar-bugs

Parse bug patterns and classify similar code occurrences as BUG, OK, or REVIEW.

Community
Advanced
lazygopherslazygophers
4

lint

Configure and execute golangci-lint for Go projects with custom linters and exclusions.

Official
Intermediate
gaia-reactgaia-react
21

eslint-fixes

Resolve ESLint violations and configuration conflicts with standardized refactoring patterns.

Official
Intermediate
VincentChong123VincentChong123

add-karpathy-llm-wiki

Maintain a persistent markdown wiki with automated ingestion and health checks.

Community
Advanced