How does the skill detect when to document a problem?

It automatically triggers when it detects confirmation phrases like 'that worked' or 'it's fixed,' and can also be manually invoked using the /doc-fix command.

What happens if a similar issue already exists?

The skill searches existing documentation and prompts you to either create a new cross-referenced document or update the existing one if the root cause is identical.

Can I use these docs to improve Claude's future behavior?

Yes, through the 'Decision Menu,' you can promote a documented solution to 'Required Reading' or extract it into a new skill to guide future code generation.

Where is the documentation stored?

Documentation is stored as markdown files within your repository's docs/solutions/ directory, organized into subdirectories based on the validated problem type.

Does it document every minor change?

No, the skill is designed to filter out trivial fixes like typos and focus on non-obvious solutions, tricky debugging sessions, and problems that require multiple investigation attempts.

Compound Problem Documentation

Name: Compound Problem Documentation
Author: Activer007

byActiver007

学習とドキュメンテーション

Capture and categorize solved technical problems into structured markdown documentation with YAML metadata for fast lookup.

概要

The Compound Docs skill automates the creation of a searchable institutional knowledge base by capturing technical resolutions immediately after a problem is confirmed fixed. It follows a rigorous 7-step workflow to extract context, validate metadata against a YAML schema, and organize solutions into specific categories. By turning transient conversation fixes into structured, searchable records, it ensures that non-trivial debugging efforts and non-obvious solutions are preserved for future sessions and cross-referenced to prevent recurring issues.

主な機能

Automatic invocation triggered by resolution confirmation phrases
Proactive cross-referencing of related issues and recurring patterns
Automated category-based file organization and sanitized naming
Post-capture menu to promote solutions to critical patterns or new skills
Strict YAML frontmatter validation for standardized metadata
0 GitHub stars

ユースケース

Maintaining institutional knowledge during complex refactoring or module development
Building a searchable repository of non-obvious bug fixes and configuration workarounds
Identifying and documenting critical coding patterns to improve team-wide code quality

概要

主な機能

Automatic invocation triggered by resolution confirmation phrases
Proactive cross-referencing of related issues and recurring patterns
Automated category-based file organization and sanitized naming
Post-capture menu to promote solutions to critical patterns or new skills
Strict YAML frontmatter validation for standardized metadata
0 GitHub stars

ユースケース

Maintaining institutional knowledge during complex refactoring or module development
Building a searchable repository of non-obvious bug fixes and configuration workarounds
Identifying and documenting critical coding patterns to improve team-wide code quality