doey-purge

Audit and purge context rot across monorepos with parallel workers.

6|2|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/FRIKKern/doey --skill doey-purge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doey-purge
Source: https://github.com/FRIKKern/doey/tree/main/.claude/skills/doey-purge
Command: npx skills add https://github.com/FRIKKern/doey --skill doey-purge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill helps teams identify and remediate context rot and outdated code across a project by performing a structured two-wave audit and fix pass, improving maintainability and reliability.

Core Features & Use Cases

  • Two-wave audit and fix: first audit for bloat, dead code, and misconfigurations, then apply safe fixes.
  • Team-based orchestration: coordinates workers to run checks in parallel, reducing turnaround time.
  • Reportable outcomes: generates per-domain purge reports to track issues and progress.

Quick Start

Run the two-wave purge workflow to audit and fix your codebase and generate per-domain reports.

Frequently Asked Questions about doey-purge

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

FAQPage Schema
How do I audit and purge context rot across a large codebase?

To audit and purge context rot across a codebase, you can run a structured two-wave workflow. It first audits for bloat, dead code, and misconfigurations, then applies safe, reviewable fixes to improve maintainability.

What does context rot mean in codebase maintenance?

Context rot in codebase maintenance refers to outdated code, configuration bloat, and misconfigurations that degrade project reliability. Auditing and purging this rot remediates these issues to improve overall maintainability.

Can I run parallel codebase audits on a multi-repo project?

Yes, you can run parallel codebase audits on multi-repo projects. The workflow coordinates parallel workers through a dispatch system to audit and fix code, config, and doc issues across both monorepos and multi-repos.

How do I fix dead code and configuration bloat safely?

To fix dead code and configuration bloat safely, use a two-wave audit-and-fix workflow. It first identifies issues across domains, then enforces safe, reviewable fixes to remediate the codebase without breaking existing logic.

Does the codebase purge workflow generate maintenance reports?

Yes, the codebase purge workflow generates maintenance reports. It produces per-domain purge reports using the runtime environment, allowing teams to track identified issues and remediation progress.

When should I not use an automated codebase purge workflow?

You should not use an automated codebase purge workflow for untracked or highly sensitive code without review. While it enforces safe fixes, teams should still review the generated per-domain reports before applying major remediation changes.