Afrexai Tech Debt Audit

What This Skill Does

The Afrexai Tech Debt Audit is a specialized agent skill designed to quantify, categorize, and prioritize technical debt within software engineering organizations. By processing user-provided descriptions of system architecture, stack components, and operational pain points, the agent performs a systematic assessment of potential bottlenecks. It evaluates debt across six primary domains: architecture, code quality, dependencies, testing coverage, infrastructure, and documentation. The skill employs a weighted scoring formula—Priority Score = (Risk × 3) + (Business Impact × 2) + (1/Effort × 1)—to transform qualitative engineering feedback into a quantitative roadmap. Beyond mere identification, the agent generates detailed remediation plans, including cost-modeling in developer hours and currency, helping teams justify refactoring efforts to stakeholders through board-ready executive summaries.

Installation

To integrate this skill into your environment, use the following OpenClaw command in your terminal: clawhub install openclaw/skills/skills/1kalin/afrexai-tech-debt-audit Ensure your agent environment has sufficient context access to the codebase metadata to derive the most accurate results.

Use Cases

This skill is ideal for engineering leads and CTOs preparing for quarterly planning or those attempting to manage 'spaghetti code' sprawl. Use it during technical audits, prior to architectural migrations, or when velocity has hit a plateau due to accumulated legacy issues. It is particularly effective for teams looking to transition from manual, high-risk deployment processes to automated CI/CD workflows.

Example Prompts

1. "Audit our technical debt. We are running a legacy Python/Django monolithic application with 250k LOC and 8 engineers. We struggle with long PR reviews, a lack of unit tests, and infrequent, high-risk releases."
2. "Analyze the tech debt in our React/Next.js frontend. We have 15 developers, lots of dependency bloat, inconsistent state management, and no automated regression testing. Give me a 30-day prioritized action plan."
3. "We are planning a migration from an on-prem data center to AWS. Based on our current setup of manual server provisioning and outdated security patches, provide an impact assessment and a roadmap for remediation."

Tips & Limitations

For best results, be as specific as possible regarding the lines of code (LOC), team size, and the specific nature of your pain points. The accuracy of the 'Carrying Cost' estimation depends entirely on the transparency of your input data. Note that this skill provides a strategic assessment based on provided context; it does not perform direct static code analysis on files and cannot 'fix' the code itself. Always validate the generated remediation roadmap against your team’s specific domain constraints before proceeding with major architectural shifts.