doc-forensic-inventory

Detect stale documentation references after code or infrastructure changes.

1|Updated Mar 6, 2026

Search Tags:#code changes #forensic audit #document inventory #doc synchronization #stale reference detection

Ready to run

npx skills add https://github.com/DaBigHomie/ugwtf --skill doc-forensic-inventory

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: doc-forensic-inventory
Source: https://github.com/DaBigHomie/ugwtf/tree/main/.cursor/skills/doc-forensic-inventory
Command: npx skills add https://github.com/DaBigHomie/ugwtf --skill doc-forensic-inventory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the update of forensic document inventories after code and infrastructure changes, identifying stale references across domains, skills, agents, scripts, and documentation.

Core Features & Use Cases

Cross-Walk Analysis: Identifies and cross-walks stale references in documentation.
Triggered Updates: Responds to code or infrastructure changes, triggers updates in documentation.
Use Case: Post-deployment or migration of a WARDEN supabase project, the Skill can ensure all related documentation remains up-to-date and accurate.

Quick Start

Run the 'doc-forensic-inventory' skill after deploying a new WARDEN supabase feature to check for any stale references in the documentation.

Frequently Asked Questions about doc-forensic-inventory

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

FAQPage Schema

How do I detect stale documentation references after code changes?▼

To detect stale documentation references after code changes, you can run an automated forensic inventory process that cross-walks source code modifications against existing documentation to identify outdated links.

What is a forensic document inventory audit?▼

A forensic document inventory audit is an analysis technique that cross-references documentation across domains, skills, and agents to locate and flag stale references following infrastructure updates.

How do I automate documentation synchronization after migrating a supabase project?▼

Automating documentation synchronization after migrating a supabase project involves triggering a forensic inventory update that cross-walks code changes to ensure all related docs remain accurate.

Do I need source code access to perform a forensic document inventory update?▼

Yes, you need access to both the source code and documentation to perform an accurate forensic document inventory update and successfully detect stale references.

Can I use a forensic inventory audit for cross-domain and cross-agent analysis?▼

Yes, forensic inventory audits perform cross-domain, cross-skill, and cross-agent analysis to comprehensively detect stale documentation references triggered by code or infrastructure changes.

What is the best way to update documentation references after a deployment?▼

The best way to update documentation references after a deployment is to trigger an automated forensic inventory check that cross-walks the new code changes to identify and update stale references.