skills.rest
jasonmichaelbell78-creator
jasonmichaelbell78-creatorCOMMUNITY
Explore all skills by this author →
GitHub

audit-refactoring

Identify technical debt in codebases by structure, duplication, and complexity.

Updated Feb 24, 2026
Search Tags:#refactoring#audit#code-quality#technical-debt#circular-dependencies#cognitive-complexity#god-objects
One-click install
npx skills add https://github.com/jasonmichaelbell78-creator/framework --skill audit-refactoring-jasonmichaelbell78-creator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit-refactoring
Source: https://github.com/jasonmichaelbell78-creator/framework/tree/main/.claude/skills/audit-refactoring
Command: npx skills add https://github.com/jasonmichaelbell78-creator/framework --skill audit-refactoring-jasonmichaelbell78-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit refactoring identifies and inventories technical debt in a codebase, focusing on structure, duplication, and complexity to guide targeted improvements.

Core Features & Use Cases

  • Parallel audit with three specialized agents to analyze god objects, complexity, and debt markers
  • Checks for circular dependencies, large files, and TODO/FIXME/HACK markers
  • Use cases include establishing baselines before major refactors and validating post-change health

Quick Start

Run the single-session refactoring audit to establish baselines and actionable findings for your codebase.

Frequently Asked Questions about audit-refactoring

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

FAQPage Schema
How do I audit technical debt and code smells in a single session?▼

You can audit technical debt in a single session by running parallel specialized agents that scan defined scopes like src/ and lib/ to inventory structural complexity, duplication, and code smells for targeted refactoring.

What are God Objects and cognitive complexity in a codebase refactoring audit?▼

God Objects are oversized modules handling too many responsibilities, while cognitive complexity measures how difficult code is to read. A refactoring audit inventories both to guide structural improvements.

Can I check for circular dependencies and TODO markers in specific directories?▼

Yes, you can configure the audit to include directories like components/ and hooks/ while excluding node_modules/ and dist/, allowing it to effectively check for circular dependencies, large files, and TODO/FIXME/HACK markers.

What is the best way to establish a baseline before a major code refactor?▼

The best way to establish a refactoring baseline is to run a comprehensive code quality audit that inventories existing technical debt, architecture violations, and code duplication before planning structural changes.

Does a single-session refactoring audit work for post-change validation?▼

Yes, a single-session refactoring audit supports post-change validation by re-scanning the codebase to verify that structural improvements successfully reduced technical debt and resolved identified code smells.

What directories should I exclude when scanning for code duplication and technical debt?▼

When scanning for code duplication and technical debt, you should exclude build artifacts and dependencies such as node_modules/, dist/, build/, and docs/ to focus the audit strictly on your source code.

Related Skills

Explore More Software Engineering Skills→
yaresimeonthomasyaresimeonthomas

ponytail-debt

Scan codebases for ponytail: comments and generate a structured debt ledger.

Community
Basic
meaganewallermeaganewaller
3

complexity-audit

Audit code modules for accidental complexity, circular dependencies, and layering violations.

Community
Advanced
CuriousLearnerCuriousLearner
27

complexity-analyzer

Measure code complexity metrics and identify high-complexity areas in software projects.

Community
Advanced
tokioutokiou
1

golang-dependency-injection

Design dependency injection wiring for Go service architectures.

Community
Advanced