qd

Audit documentation for drift and staleness against code and product docs.

Updated Aug 23, 2026

Search Tags:#documentation #qa #audit #readme #drift #code

Ready to run

npx skills add https://github.com/madebymlai/feldspar --skill qd-madebymlai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qd
Source: https://github.com/madebymlai/feldspar/tree/main/.claude/skills/qd
Command: npx skills add https://github.com/madebymlai/feldspar --skill qd-madebymlai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation QA audit identifies stale docs and drift between code, docs, and references, improving accuracy and consistency across projects.

Core Features & Use Cases

Detects documentation drift between code and docs across READMEs, API docs, and inline references.
Verifies alignment of documentation with current implementation, surfacing outdated or conflicting information for remediation.
Use Case: In a multi-repo software project, run audits to surface outdated API references and mismatches between behavior and documentation.

Quick Start

Run a documentation audit on the target repository to identify stale docs and code/doc drift, and generate a drift report.

Frequently Asked Questions about qd

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

FAQPage Schema

How do I detect documentation drift between my code and READMEs?▼

To detect documentation drift, you can audit your documentation against the current code implementation to surface outdated references and mismatches in READMEs, API docs, and inline comments. This generates a comprehensive drift report for remediation.

What is a documentation QA audit and how does it work?▼

A documentation QA audit identifies stale docs and verifies alignment between code and product docs. It works by scanning repositories to flag outdated API references and conflicting information, reporting drift against a baseline for improved accuracy and consistency across projects.

Can I run documentation staleness checks on a large multi-repo project?▼

Yes, you can run documentation staleness checks on large multi-repo projects. The audit applies to repository health checks across small to large projects, verifying alignment of documentation with current implementation and surfacing outdated references.

How do I configure thresholds for flagging outdated API references?▼

You can configure thresholds to flag outdated API references by setting specific parameters before running the audit. This allows you to control the sensitivity of the drift detection process and customize automation hooks for your repository health checks.

What's the best way to automate documentation alignment checks for inline comments?▼

The best way to automate documentation alignment checks is by using automation hooks provided by the audit tool. This enables continuous verification of inline comments and references against a baseline, automatically flagging conflicts and outdated information for remediation.