qd

Detect stale documentation by comparing docs against current code and APIs.

6|2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/skillsets-cc/main --skill qd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qd
Source: https://github.com/skillsets-cc/main/tree/main/skillsets/%40supercollectible/Valence/content/.claude/skills/qd
Command: npx skills add https://github.com/skillsets-cc/main --skill qd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation QA audit helps teams verify that product and technical documentation stays accurate, up-to-date, and aligned with code and builds, reducing drift and confusion.

Core Features & Use Cases

  • Automated drift detection across docs and code
  • Version-aware QA checks that flag stale or conflicting content
  • Use Case: When releasing a software update, run the audit to ensure docs reflect the latest API surface and usage notes.

Quick Start

Run a documentation audit across the target repository to identify stale content and drift and report findings.

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 against current code and APIs?▼

Documentation drift is detected by running an automated audit that compares docs against current code and APIs to surface stale references, version notes, and cross-links, ensuring technical content stays aligned with evolving software.

What is version-aware QA for technical documentation?▼

Version-aware QA checks documentation for stale or conflicting content by validating references and cross-links against the latest API surface, flagging outdated usage notes before a software release.

Can I run a documentation audit across multi-repo software projects?▼

Yes, you can run documentation audits across multi-repo structures to identify drift and ensure consistency, verifying that technical docs accurately reflect the current API surface and usage notes.

What's the best way to check cross-links and references for alignment before a release?▼

The best way to check cross-links and references for alignment is applying a docs-aware auditing engine that validates version notes and cross-links against current code, reporting stale content before release.

Does documentation QA review flag outdated version notes and conflicting content?▼

Documentation QA review flags outdated version notes and conflicting content by applying version-aware checks, ensuring technical documentation stays accurate, up-to-date, and aligned with current builds.