Skip to content

donaldfilimon/abi / .agents/skills/codebase-analysis

codebase-analysis

Verified

This skill should be used when the user asks to find legacy patterns, technical debt, or modernization targets in ABI — e.g. 'where should we start modernizing this module', 'find outdated patterns in crates/', 'audit this file for tech debt' — before any refactor begins.

FileKindSize
SKILL.mdskill md1.6 KB
references/analysis-checklist.mdmarkdown2.5 KB
---
name: codebase-analysis
description: This skill should be used when the user asks to find legacy patterns, technical debt, or modernization targets in ABI — e.g. 'where should we start modernizing this module', 'find outdated patterns in crates/', 'audit this file for tech debt' — before any refactor begins.
---

# Codebase Analysis

Systematic techniques to discover technical debt, outdated patterns, and high-value modernization targets.

## Process

1. Identify boundaries and modules.
2. Look for:
   - Stringly-typed state and magic values.
   - Broad exception catching or error ignoring.
   - God classes / large files.
   - Tight coupling to outdated frameworks or stdlib workarounds.
   - Missing or weak typing.
   - Manual resource management that modern constructs solve.
3. Prioritize by impact and risk (use the strategy skill).
4. Produce a modernization opportunity report with evidence (code locations + rationale).

## Heuristics

- Any place using "TODO: modernize" or historical comments.
- Code that duplicates what the language now provides natively.
- Areas with high churn + high bug rate.
- Modules that are hard to test in isolation.

## Additional Resources

- `.agents/skills/codebase-analysis/references/analysis-checklist.md` — structured scan + prioritization table
- Use Grep + Glob heavily for pattern hunting.

Output should be actionable for the planner agent and strategy skill.

Base directory for this skill: /Users/donald/sources/repos/abi/.agents/skills/codebase-analysis
Relative paths in this skill (e.g., references/) are relative to this base directory.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall