blame-doc

Analyze MDX documentation for duplicates, outdated content, and codebase discrepancies.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/brainfish-ai/devdoc --skill blame-doc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blame-doc
Source: https://github.com/brainfish-ai/devdoc/tree/main/public-apis/meta/.claude/skills/blame-doc
Command: npx skills add https://github.com/brainfish-ai/devdoc --skill blame-doc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes documentation quality by identifying duplicates, outdated content, and discrepancies with the codebase, enabling teams to maintain clean, consistent docs.

Core Features & Use Cases

  • Documentation quality analysis: Detect duplicates, outdated sections, and cross-file inconsistencies.
  • Codebase alignment: Compare documented APIs and exports with actual source.
  • Use Case: Given a large MDX repository, generate a report of redundant pages and mismatches to guide a remediation sprint.

Quick Start

Run the blame-doc skill to generate a report on documentation health across the repository.

Frequently Asked Questions about blame-doc

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

FAQPage Schema
How do I analyze documentation quality to find duplicates and outdated content?

To analyze documentation quality, you can scan all MDX files across your repository to surface duplicate sections, outdated content, and cross-file inconsistencies, generating a comprehensive health report for your docs.

What is the best way to check if my MDX documentation matches the actual codebase exports?

Checking MDX documentation against your codebase involves comparing documented APIs, components, and configurations with the actual source code exports to identify discrepancies and mismatches that need remediation.

Does documentation analysis require reading configuration files like docs.json?

Yes, documentation analysis requires reading docs.json and .devdoc/context.json if present to accurately cross-reference documented APIs and configurations against the actual source code exports.

How do I generate a report of redundant MDX pages and codebase mismatches?

Generating a report of redundant pages and mismatches is done by running a documentation analysis scan across the repository, which identifies duplicates, outdated sections, and discrepancies to guide your remediation sprint.

What are the limitations of automated documentation quality analysis?

Automated documentation quality analysis focuses on MDX files and source code exports, requiring docs.json and context.json for accurate cross-referencing, but may not capture semantic inconsistencies or subjective content quality issues.