CtrlK
BlogDocsLog inGet started
Tessl Logo

code-refactoring-tech-debt

You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti

Install with Tessl CLI

npx tessl i github:sickn33/antigravity-awesome-skills --skill code-refactoring-tech-debt
What are skills?

49

1.43x

Quality

30%

Does it follow best practices?

Impact

73%

1.43x

Average score across 3 eval scenarios

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/code-refactoring-tech-debt/SKILL.md
SKILL.md
Review
Evals

Evaluation results

77%

33%

Legacy E-Commerce Backend: Technical Debt Assessment

Debt inventory taxonomy and cost assessment

Criteria
Without context
With context

Complexity threshold

100%

80%

Long method threshold

0%

100%

God class definition

0%

0%

Nesting threshold

0%

25%

Duplication quantified

50%

100%

Dollar cost calculation

100%

100%

Risk classification

100%

100%

YAML metrics dashboard

0%

100%

Python trend dict

0%

12%

Three-tier roadmap

40%

100%

All seven output sections

66%

100%

Without context: $0.5001 · 3m 19s · 10 turns · 11 in / 9,895 out tokens

With context: $0.8867 · 4m 18s · 26 turns · 59 in / 13,661 out tokens

70%

17%

Engineering Quality Governance Rollout

Prevention strategy and quality governance

Criteria
Without context
With context

Max complexity gate

75%

100%

Max duplication gate

62%

0%

Min coverage gate

87%

100%

CI pipeline checks

37%

100%

Two-approval review

100%

100%

Review test and docs requirement

100%

100%

Sprint allocation 20%

100%

100%

Debt budget increase limit

0%

100%

Debt budget reduction mandate

0%

0%

Three tracking tools named

100%

100%

Code standard method length

0%

0%

Code standard class length

0%

0%

Monthly success metrics

0%

75%

Without context: $0.3027 · 1m 57s · 8 turns · 9 in / 6,635 out tokens

With context: $0.6393 · 3m 25s · 18 turns · 16 in / 11,568 out tokens

74%

18%

Legacy Billing Engine Modernization

Incremental refactoring implementation strategy

Criteria
Without context
With context

Phase 1: Facade

33%

50%

Phase 2: Parallel service

83%

91%

Phase 3: Feature flag migration

83%

100%

Backward compatibility

100%

100%

Test before refactoring

100%

100%

Document architectural decisions

12%

37%

Measure impact with metrics

87%

100%

Method length standard

0%

25%

Class length standard

0%

0%

Complexity standard

0%

100%

Coverage standard

100%

100%

Without context: $0.3929 · 2m 4s · 12 turns · 61 in / 7,402 out tokens

With context: $0.6278 · 3m 20s · 18 turns · 65 in / 11,025 out tokens

Evaluated
Agent
Claude Code
Model
Claude Sonnet 4.6

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.