fix-reporter

Capture solved problems as categorized Markdown docs with YAML frontmatter.

47|11|Updated Nov 26, 2025
One-click install
npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill fix-reporter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-reporter
Source: https://github.com/majesticlabs-dev/majestic-marketplace/tree/main/plugins/majestic-engineer/skills/fix-reporter
Command: npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill fix-reporter

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill captures solved problems with YAML frontmatter to build a categorized, searchable knowledge base for future reference.

Core Features & Use Cases

  • Documentation Capture: Standardized templates for root-cause and resolution.
  • YAML Frontmatter Schema: Enforces metadata quality and categorization.
  • Searchable Outputs: Structured knowledge for faster problem resolution.

Quick Start

Create a fix report after a confirmed resolution and store it under docs/solutions with proper categorization.

Frequently Asked Questions about fix-reporter

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

FAQPage Schema
How do I document solved problems in a searchable knowledge base?

Capture solved problems as categorized Markdown documentation with YAML frontmatter metadata. The Skill generates structured docs under docs/solutions organized by symptom category and module, including investigation, root cause, resolution, and prevention details, making past solutions instantly searchable.

What should I include in a fix report for consistent knowledge capture?

Fix reports enforce a seven-step process capturing investigation steps, root cause analysis, resolution steps, and prevention measures. YAML frontmatter validates metadata against schema.yaml, ensuring consistent categorization by symptom and module so knowledge remains organized and discoverable.

Can I standardize troubleshooting documentation across my team?

Yes. YAML frontmatter schemas enforce metadata quality and categorization standards across all fix reports. This standardization creates consistent, searchable documentation that teams can reference when solving recurring problems, reducing resolution time.

How does YAML frontmatter improve knowledge base organization?

YAML frontmatter provides structured metadata validation that categorizes solutions by symptom and module. This metadata-driven organization enables fast filtering and search, transforming ad-hoc troubleshooting notes into a queryable knowledge base.

When should I create a fix report after resolving an issue?

Create a fix report immediately after confirming a resolution to capture the investigation and solution while details are fresh. Store it under docs/solutions with proper categorization so future occurrences of the same problem are resolved faster.

Related Skills