SkillVaultskills Browse all 500 skills

Maintenance · Version 1.2.0 · Reviewed 2026-08-02

Code Complexity Hotspot Analyst

Reduce change risk for hotspot detection and change coupling with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Locates the code where complexity and change frequency intersect, which is where defects concentrate.

₹99 one-time

Get this skill archive

What this skill helps you do

  • Hotspot detection
  • Change coupling
  • Refactor targeting

How Code Complexity Hotspot Analyst works

You provide

Current versions, changelogs, support dates, and coverage

It inspects

Breaking changes and transitive pins behind hotspot detection

It decides

A change coupling sequence taking one major at a time

You verify

Suite green between increments with rollback proven

What it checks first

Code Complexity Hotspot Analyst locates the code where complexity and change frequency intersect, which is where defects concentrate. Use it when the work involves Hotspot detection, Change coupling, Refactor targeting.

  1. Whether the current version is still supported, and the date support actually ends.
  2. How many major versions separate current from target, since each carries its own breaking changes.
  3. Whether test coverage is sufficient to detect a behavioral regression from the upgrade.
  4. Transitive dependencies that constrain the upgrade regardless of direct requirements.

Failure modes it recognizes

  • Skipping intermediate majors so several sets of breaking changes land together, unattributable.
  • A deprecation warning ignored until the removal makes the upgrade a project.
  • A transitive dependency pinning an old version, silently blocking the direct upgrade.
  • An upgrade completed without a rollback path because a data format changed.

Answers it will reject

  • Upgrading everything at once to reduce disruption, which maximizes debugging cost.
  • Treating a green build as sufficient evidence when coverage of the changed behavior is thin.
  • Deferring an end-of-life migration until support has already lapsed.

Decision rules it applies

  • Upgrade one major at a time with the suite green between each step.
  • Resolve deprecation warnings from version N before starting N+1; they are the removal list.
  • Plan end-of-life migrations against the support date, not against convenience.

Evidence it asks for

  • Inventory direct and transitive versions against their support timelines.
  • Run the suite between each increment and record which behavior changed.
  • Verify rollback by deploying the previous version against the upgraded data.

The method inside

  1. Establish what is actually true about hotspot detection from the supplied evidence, and mark what is missing.
  2. Identify the mechanism behind change coupling rather than restating the symptom.
  3. Choose the smallest defensible change for refactor targeting, weighing impact, confidence, effort, and reversibility.
  4. Define rollback and post-upgrade observation

Deliverables

  • Hotspot detection assessment
  • Change coupling decision and action plan
  • Refactor targeting verification checklist

Evidence requirements

  • Current and target versions
  • Dependency graph and changelogs
  • Tests, compatibility constraints, and rollout environment

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

We want to reduce defects but our codebase is large. Where should refactoring effort actually go?

Expected output

Complexity alone is a weak predictor, because complex code nobody touches is harmless. Intersect cyclomatic complexity with change frequency and incident history; the small overlap is where defects concentrate and where refactoring pays back...

Boundaries and compatibility

Ideal for

  • Hotspot detection: produce a decision or artifact grounded in supplied evidence.
  • Change coupling: produce a decision or artifact grounded in supplied evidence.
  • Refactor targeting: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Blindly upgrading across multiple major versions
  • Assuming semantic versioning guarantees compatibility

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.