archivist-duplication-auditor

Identify duplicated logic across Project Archivist implementations and write audit reports.

Updated Aug 27, 2026

Search Tags:#audit #reporting #duplication #inventory #code-audit #project-archivist

Ready to run

npx skills add https://github.com/rfowler1994/project-archivist --skill archivist-duplication-auditor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: archivist-duplication-auditor
Source: https://github.com/rfowler1994/project-archivist/tree/main/.agents/skills/archivist-duplication-auditor
Command: npx skills add https://github.com/rfowler1994/project-archivist --skill archivist-duplication-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archivist Duplication Auditor helps teams identify risky, duplicated or near-duplicated logic across the Project Archivist codebase without applying changes.

Core Features & Use Cases

Reads inventory files and compares implementations to identify behavior drift across date/time handling, validation/normalization, DTO/request/response mapping, lifecycle actions, custom field handling, API error mapping, and common UI/component patterns.
Produces a structured report under docs/code-audits/reports/ documenting findings and suggested mitigations.
Keeps remediation suggestions lightweight, avoiding automatic edits or migrations to preserve intentional design.

Quick Start

Run archivist-duplication-auditor against the target project to generate a duplication audit report.

Frequently Asked Questions about archivist-duplication-auditor

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

FAQPage Schema

How do I detect duplicated logic across a codebase without modifying source files?▼

To audit duplicate code without modifying files, compare inventory implementations for behavior drift across date/time handling and validation. The auditor writes a formal report under docs/code-audits/reports/, identifying duplicates while avoiding automatic edits to preserve intentional design.

What is behavior drift in duplicated code and how is it identified?▼

Behavior drift occurs when copied logic diverges over time. It is identified by reading inventory files and comparing implementations across areas like DTO mapping, lifecycle actions, and API error mapping to detect near-duplicated logic that has functionally diverged from the original pattern.

How do I generate a code audit report for duplicated UI component patterns?▼

Generate a code audit report by running the auditor against your target project. It compares repeated UI and component patterns, writes findings to docs/code-audits/reports/, and suggests lightweight remediation mitigations without applying automatic migrations or edits to the source.

Does the duplication auditor apply automatic fixes or migrations to resolve findings?▼

No, the duplication auditor does not apply automatic fixes or migrations. It keeps remediation suggestions lightweight, producing a structured report documenting findings while preserving intentional design by avoiding automatic edits to the codebase.

Can I audit custom field handling and list query helpers for near-duplicate logic?▼

Yes, you can audit custom field handling and list/query helpers for near-duplicate logic. The auditor specifically targets these areas, alongside validation and date/time handling, reading inventory to compare implementations and report any behavior drift.