skills.rest
dthompson-jti
dthompson-jtiCOMMUNITY
Explore all skills by this author →
GitHub

audit-refactor-opportunities

Identifies code smells and refactoring opportunities in JavaScript/TypeScript projects.

Updated Aug 23, 2026
Search Tags:#refactor#code-quality#duplication#dead-code#code-smells#tech-debt#pattern-violations
One-click install
npx skills add https://github.com/dthompson-jti/safety-check-app-concept --skill audit-refactor-opportunities
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit-refactor-opportunities
Source: https://github.com/dthompson-jti/safety-check-app-concept/tree/main/.agent/skills/audit/refactor-opportunities
Command: npx skills add https://github.com/dthompson-jti/safety-check-app-concept --skill audit-refactor-opportunities

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify code smells and refactoring opportunities without applying fixes to the codebase, helping teams plan improvements without introducing risk.

Core Features & Use Cases

  • Detect code smells such as duplication, long functions, deep nesting, and dead code.
  • Flag inconsistent patterns and naming for consistency across the project.
  • Produce a prioritized list of refactor opportunities with estimated effort to guide sprint planning.

Quick Start

Run a pre-audit for invariants and produce a prioritized list of refactor opportunities with effort estimates.

Frequently Asked Questions about audit-refactor-opportunities

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

FAQPage Schema
How do I detect code smells and refactoring opportunities without modifying the codebase?▼

You can detect code smells and refactoring opportunities by running a pre-audit that identifies duplication, long functions, dead code, and pattern violations without applying any fixes, ensuring the codebase remains unchanged during tech debt assessments.

Can I identify dead code and duplication across multi-file JavaScript and TypeScript projects?▼

Yes, you can identify dead code and duplication across multi-file JavaScript and TypeScript projects by analyzing the codebase for structural issues, inconsistent naming, and pattern violations to support codebase health checks and refactor planning.

What is the best way to prioritize tech debt for sprint planning?▼

The best way to prioritize tech debt is to generate a prioritized list of refactor opportunities complete with effort estimates, helping teams sequence code quality improvements and pattern violation fixes during sprint planning sessions.

Does this code quality analysis flag inconsistent naming and pattern violations?▼

Yes, this code quality analysis flags inconsistent naming and pattern violations across the project, ensuring teams can assess consistency and identify deep nesting or long functions without introducing risk by altering the code.

How do I perform a codebase health check for tech debt without introducing risk?▼

You perform a codebase health check by scanning for code smells like duplication, dead code, and deep nesting to produce a prioritized refactor list with effort estimates, completely avoiding fixes that would introduce risk into the codebase.

Related Skills

Explore More Software Engineering Skills→
CygnusfearCygnusfear
5

architectural-analysis

Diagnose architectural health issues in TypeScript/JavaScript codebases and output a structured findings report.

Community
Basic
sun2443sun2443

tech-debt

Categorize and prioritize technical debt with impact, risk, and effort scores.

Community
Intermediate
MMXCMMXC

pr-reviewer

Analyze GitHub pull request diffs for security, error handling, and style issues.

Community
Advanced
applewaveapplewave
1

phase-8-review

Verify codebase quality and architectural conformance across project phases.

Community
Advanced