Can I customize the documentation format?

The skill uses a standardized resolution template and YAML schema to ensure consistency, but these can be extended through the repository's asset files.

Does it handle recurring issues?

Yes, the skill includes a critical pattern detection feature that suggests promoting solutions to a 'Required Reading' file if a similar issue occurs multiple times.

Where is the documentation stored?

Documentation is stored as Markdown files in specific subdirectories within docs/solutions/, organized by problem category for fast lookup.

What kind of metadata does it capture?

It captures module names, symptoms, investigation attempts, root causes, solution steps, environment details (like Rails or OS versions), and severity levels.

How does the skill detect when a problem is solved?

The skill auto-invokes when it detects phrases like 'that worked' or 'it's fixed', and can also be manually triggered via the /doc-fix or /compound commands.

Categorized Solution Documenter

Name: Categorized Solution Documenter
Author: Activer007

byActiver007

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

Captures and organizes solved technical problems into a searchable knowledge base with validated YAML metadata.

概要

The Compound Docs skill automates the creation of institutional knowledge by documenting successfully resolved bugs and architectural challenges immediately upon confirmation. It uses a structured 7-step process to extract technical context from conversations, validate metadata against strict YAML schemas, and organize files into categorized directories. By turning transient chat resolutions into permanent, searchable documentation, it ensures that non-obvious fixes and root cause analyses are available for future AI sessions and team members, preventing the repetition of past mistakes.

主な機能

Automated directory organization based on enum-validated problem types
0 GitHub stars
Cross-referencing logic to connect related issues and detect recurring patterns
Strict YAML frontmatter validation for consistent metadata and searchability
Interactive post-capture menu for promoting critical solutions to required reading
Automatic invocation based on problem resolution phrases

ユースケース

Building a searchable institutional knowledge base of complex debugging sessions
Identifying and documenting systemic architectural patterns and critical fixes
Maintaining a 'lessons learned' repository for specific software modules and environments

概要

主な機能

Automated directory organization based on enum-validated problem types
0 GitHub stars
Cross-referencing logic to connect related issues and detect recurring patterns
Strict YAML frontmatter validation for consistent metadata and searchability
Interactive post-capture menu for promoting critical solutions to required reading
Automatic invocation based on problem resolution phrases

ユースケース

Building a searchable institutional knowledge base of complex debugging sessions
Identifying and documenting systemic architectural patterns and critical fixes
Maintaining a 'lessons learned' repository for specific software modules and environments