blame-doc

Analyze repository docs and code to produce a structured blame report.

60|2|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/reasondb/reasondb --skill blame-doc-reasondb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blame-doc
Source: https://github.com/reasondb/reasondb/tree/main/docs/.claude/skills/blame-doc
Command: npx skills add https://github.com/reasondb/reasondb --skill blame-doc-reasondb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation quality issues undermine trust and maintainability. This Skill identifies duplicates, outdated content, and discrepancies with the codebase to help teams keep documentation accurate and reliable.

Core Features & Use Cases

  • Automated blame reports that surface duplicates, outdated content, and inconsistencies across documentation.
  • Cross-referencing with the codebase to surface mismatches between docs and implementation.
  • Actionable recommendations to fix issues and improve ongoing documentation maintenance.

Quick Start

Run blame-doc across your repository to generate a comprehensive documentation blame report.

Frequently Asked Questions about blame-doc

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

FAQPage Schema
How do I find outdated documentation and mismatches in my codebase?

Cross-referencing docs against your codebase identifies outdated content and implementation mismatches. This process generates a structured blame report that highlights discrepancies without modifying source files.

What is a documentation blame report and what does it contain?

A documentation blame report is a standardized, action-oriented output detailing critical findings on docs quality. It surfaces duplicate content, outdated references, and codebase discrepancies alongside actionable recommendations and warnings.

How do I detect duplicate content across my repository's documentation?

Run an automated analysis across all repository docs and code artifacts to detect duplicate content. This generates a comprehensive report identifying redundant entries and quality issues to help maintain accuracy.

Can I generate documentation quality reports without modifying source files?

Yes, you can generate documentation quality reports without modifying source files. The analysis reads existing docs and code artifacts exclusively to output insights, ensuring your repository source code remains untouched during review.

What is the best way to surface codebase discrepancies in project documentation?

Cross-referencing your implementation directly with existing documentation is the best way to surface codebase discrepancies. This produces a structured report with critical warnings, pinpointing exactly where docs diverge from actual code logic.