vibe-redundancy-audit

Detect redundant or stale business logic across multi-layer codebases.

6|Updated Feb 5, 2026

Search Tags:#handoff #risk-assessment #redundancy #architecture-analysis #code-audit #vibe3

Ready to run

npx skills add https://github.com/jacobcy/vibe-coding-control-center --skill vibe-redundancy-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vibe-redundancy-audit
Source: https://github.com/jacobcy/vibe-coding-control-center/tree/main/skills/vibe-redundancy-audit
Command: npx skills add https://github.com/jacobcy/vibe-coding-control-center --skill vibe-redundancy-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps identify and report suspicious redundant or stale business logic across codebases, highlighting where migration residues and duplicated decision-making linger in multi-layer architectures.

Core Features & Use Cases

Detect migration residue and duplicated orchestration across command/usecase/service boundaries.
Produce evidence-based points, rationales, and recommendations for human review, not automatic cleanup.
Write audit results to the handoff system for traceability and downstream agent actions.

Quick Start

Run the redundancy audit on your current changes to generate a suspicious-points report and write a handoff.

Frequently Asked Questions about vibe-redundancy-audit

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

FAQPage Schema

How do I find redundant business logic across multi-layer architecture branches?▼

You can find redundant business logic across multi-layer architectures by running a non-destructive code audit that identifies duplicated orchestration and migration remnants across command, usecase, and service boundaries, generating an evidence-based report for review.

What is migration residue in a codebase and how do I detect it?▼

Migration residue is stale decision-making logic that lingers across branches and commits after updates. A code audit detects this suspicious logic by analyzing multi-layer architecture paths and producing evidence-based points and rationales without modifying code.

How do I audit stale code for duplicated decisions without modifying files?▼

You can audit stale code non-destructively by analyzing compatibility paths and service boundaries to identify suspicious logic. The audit generates evidence-based findings and recommendations for human review, ensuring no code is modified or deleted.

Can I trace code audit findings for downstream agent processing?▼

Yes, you can trace code audit findings by utilizing an automatic handoff logging system. The audit writes results to a reports directory, enabling downstream agents to access the evidence-based findings of suspicious redundant logic.

Does the redundancy audit automatically clean up duplicated orchestration code?▼

No, the redundancy audit does not automatically clean up code. It produces evidence-based points, rationales, and recommendations for duplicated orchestration across boundaries strictly for human review, maintaining a non-destructive analysis approach.

When do I need a redundancy audit for my multi-layer architecture?▼

You need a redundancy audit when your multi-layer architecture accumulates duplicated decisions across command, usecase, and service boundaries, or when migration remnants linger across branches and commits, requiring evidence-based risk-assessment.