modernization-assessment

Assess codebases for tech debt, deprecated dependencies, and outdated patterns.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/EmeaAppGbb/spec2cloud-microhack-greenfield --skill modernization-assessment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: modernization-assessment
Source: https://github.com/EmeaAppGbb/spec2cloud-microhack-greenfield/tree/main/.github/skills/modernization-assessment
Command: npx skills add https://github.com/EmeaAppGbb/spec2cloud-microhack-greenfield --skill modernization-assessment

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill simplifies the process of modernizing existing codebases by providing a systematic assessment of potential improvements, prioritizing actions based on severity, effort, and impact.

Core Features & Use Cases

  • Comprehensive Assessment: Evaluate codebases for technical debt, deprecated dependencies, outdated patterns, and architectural improvements.
  • Adaptive Depth: Begin with a surface-level scan and escalate analysis based on findings, including dependency age analysis, deprecated API usage, and linter warnings.
  • Output ADRs: Generate Architecture Decision Records (ADRs) for significant decisions, guiding the modernization process.

Quick Start

Run the 'modernization-assessment' skill to assess your codebase.

Frequently Asked Questions about modernization-assessment

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

FAQPage Schema
How do I assess technical debt and deprecated dependencies for a codebase modernization?

The modernization-assessment skill evaluates codebases for technical debt, deprecated dependencies, and outdated patterns. It begins with a surface-level scan and escalates analysis based on findings, prioritizing actions by severity, effort, and impact.

What is the best way to generate Architecture Decision Records for modernization initiatives?

Generating Architecture Decision Records (ADRs) for modernization initiatives involves evaluating existing codebases to identify significant architectural decisions. The skill automatically produces ADRs to guide and document the modernization process.

How does adaptive depth analysis work when evaluating outdated patterns in a codebase?

Adaptive depth analysis works by starting with a surface-level scan of the codebase and escalating evaluation based on findings. It progressively analyzes dependency ages, deprecated API usage, and linter warnings to uncover outdated patterns.

Do I need to provide documentation and codebase access to evaluate modernization opportunities?

Yes, you need to provide codebase and documentation access to evaluate modernization opportunities. This access is required to accurately assess technical debt, deprecated dependencies, and generate architecture decision records.

What limitations should I anticipate when running a codebase assessment for technical debt?

When running a codebase assessment for technical debt, anticipate limitations related to the adaptive depth of the scan. The initial surface-level analysis may not capture all deprecated API usage until the scan escalates based on initial findings.