skills.rest
Hopin-inc
Hopin-incOFFICIAL
Explore all skills by this author →
GitHub

legacy-audit

Analyze TypeScript files and commit history to quantify technical debt and generate prioritized refactor roadmaps.

3|2|Updated Jun 25, 2024
Search Tags:#code quality#typescript#audit#ddd#technical debt#legacy code#refactor roadmap
One-click install
npx skills add https://github.com/Hopin-inc/civicship-api --skill legacy-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: legacy-audit
Source: https://github.com/Hopin-inc/civicship-api/tree/main/.claude/skills/legacy-audit
Command: npx skills add https://github.com/Hopin-inc/civicship-api --skill legacy-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit and quantify legacy code to reveal technical debt, enabling targeted refactors and efficient improvement planning.

Core Features & Use Cases

  • Collects codebase statistics and historical data to surface debt hotspots.
  • Generates a prioritized refactor roadmap with domain- or file-level recommendations.
  • Supports domain-wide audits, file-specific audits, and project-wide scans for flexible workflows.

Quick Start

Audit a domain with /legacy-audit wallet or inspect a specific file with /legacy-audit src/application/domain/... to begin.

Frequently Asked Questions about legacy-audit

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

FAQPage Schema
How do I quantify technical debt in a TypeScript codebase?▼

To quantify technical debt in a TypeScript codebase, you analyze domain-level files and commit history to identify debt hotspots. This process collects codebase statistics and historical data to surface actionable areas for targeted refactoring.

What is the best way to generate a refactor roadmap for legacy code?▼

The best way to generate a refactor roadmap for legacy code is by performing an audit that analyzes domain-level TypeScript files and commit history. This yields a structured report with statistics and prioritized recommendations for file- or domain-level improvements.

Can I audit technical debt for a specific domain instead of a full project scan?▼

Yes, you can audit technical debt for a specific domain instead of a full project scan. The audit supports domain-wide audits, file-specific checks, and project-wide scans, enforcing targeted scope to produce focused, actionable refactoring guidance.

How does analyzing commit history help reveal technical debt?▼

Analyzing commit history helps reveal technical debt by tracking historical data and codebase statistics to surface debt hotspots. This historical context identifies frequently modified or problematic areas, enabling a prioritized refactor roadmap.

Do I need Domain-Driven Design to audit legacy TypeScript files?▼

You do not explicitly need Domain-Driven Design to audit legacy TypeScript files, but the audit targets domain-level files. Analyzing these domain-level TypeScript files and commit history allows the tool to quantify debt and generate actionable guidance.

Related Skills

Explore More Software Engineering Skills→
pradeepmoulipradeepmouli
2

speckit-workflows.baseline

Execute a script to generate baseline-spec.md and current-state.md from JSON output.

Community
Advanced
ailabs-393ailabs-393
438

tech-debt-analyzer

Identify and quantify technical debt across multi-language codebases.

Community
Intermediate
andy4917andy4917

ts-structure-code-review

Analyze TypeScript code for architectural weaknesses, type inconsistencies, and error handling gaps.

Community
Advanced
PearlThoughtsPearlThoughts
1

software-architect

Analyze codebases with a six-layer framework for structure, patterns, and modernization.

Official
Basic