What does the Code Archaeologist skill do?

It analyzes your codebase to find legacy patterns, helps you decide between refactoring or maintaining local consistency, and documents those decisions.

How does it help with technical debt?

By mapping old vs. new patterns, it prevents 'half-baked' refactors and ensures that every change is a deliberate architectural choice.

Can it generate documentation?

Yes, it specifically helps record the trade-offs of refactoring decisions in Architecture Decision Records (ADRs).

When should I use this skill?

Use it during code reviews, migrations, or when you encounter unfamiliar patterns in a legacy repository.

Code Archaeologist

Name: Code Archaeologist
Author: CheekyCodexConjurer

byCheekyCodexConjurer

0•

Developer Tools

Identifies legacy code patterns and provides structured guidance for consistent refactoring or compatibility maintenance.

Code Archaeologist helps developers navigate complex codebases by detecting outdated patterns and comparing them against modern standards. It prevents inconsistent refactors by forcing a conscious decision between global modernization and maintaining local consistency, ultimately documenting these technical choices through Architecture Decision Records (ADRs). This skill is essential for teams managing technical debt or migrating large-scale environments where maintaining architectural integrity is critical.

Key Features

010 GitHub stars

02Maps architectural inconsistencies across the codebase

03Generates Architecture Decision Records (ADRs) to document trade-offs

04Ensures local code consistency during incremental refactors

05Recommends modernization strategies based on specific context

06Detects legacy vs. modern coding patterns automatically

Use Cases

01Maintaining consistency in repositories with mixed legacy and modern coding styles

02Auditing a codebase before starting a large-scale migration to identify technical debt

03Onboarding to a new project and mapping out established vs. deprecated patterns

Key Features

010 GitHub stars

02Maps architectural inconsistencies across the codebase

03Generates Architecture Decision Records (ADRs) to document trade-offs

04Ensures local code consistency during incremental refactors

05Recommends modernization strategies based on specific context

06Detects legacy vs. modern coding patterns automatically

Use Cases

01Maintaining consistency in repositories with mixed legacy and modern coding styles

02Auditing a codebase before starting a large-scale migration to identify technical debt

03Onboarding to a new project and mapping out established vs. deprecated patterns