audit-drift

Detect inconsistencies and outdated references in project documentation using grep.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/dformoso/positronic --skill audit-drift-dformoso
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-drift
Source: https://github.com/dformoso/positronic/tree/main/skills/shipping/audit-drift
Command: npx skills add https://github.com/dformoso/positronic --skill audit-drift-dformoso

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill detects inconsistencies and outdated references in project documentation to ensure quality and coherence before deployment.

Core Features & Use Cases

  • Documentation Auditing: Identifies inconsistencies in project documents like PRDs, harnesses, surfaces, MCP-servers, and runtime profiles.
  • Drift Reporting: Reports on inconsistencies, dead cross-references, and contradictions between documentation and the codebase.
  • Use Case: Before shipping a project, use the audit-drift skill to automatically scan for potential issues in the documentation to maintain quality and prevent deployment errors.

Quick Start

Run the audit-drift skill to check for documentation drift in the current project.

Frequently Asked Questions about audit-drift

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

FAQPage Schema
How do I detect documentation drift before deployment?

Detect documentation drift by scanning the project repository for inconsistencies, dead cross-references, and contradictions between Markdown documents and the codebase. This ensures documentation quality and coherence prior to shipping.

What is documentation drift detection in a codebase?

Documentation drift detection identifies outdated references and inconsistencies across project files like PRDs and runtime profiles. It uses command-line tools to parse Markdown files and report contradictions between documentation and the current codebase.

How do I audit project documentation for inconsistencies?

Audit project documentation by running an automated scan across the directory structure to identify dead cross-references and contradictions. It parses Markdown files using grep and other command-line tools to report drift before deployment.

Do I need specific dependencies to check for dead cross-references in Markdown files?

No specific dependencies are required to check for dead cross-references. The process relies on standard command-line tools like grep to parse Markdown files and analyze the project directory structure for documentation inconsistencies.

Can I automate pre-deployment audits for runtime profiles and PRDs?

Yes, you can automate pre-deployment audits for runtime profiles, PRDs, and other project documents. The scan automatically detects drift, reporting inconsistencies and outdated references across the repository to prevent deployment errors.