skills.rest
fmbp1981-hash
fmbp1981-hashCOMMUNITY
Explore all skills by this author →
GitHub

code-audit

Audit codebases against IntelliX clean architecture standards and generate reports.

Updated Dec 13, 2025
Search Tags:#clean architecture#technical debt#code audit#code improvement#system review
One-click install
npx skills add https://github.com/fmbp1981-hash/cavendish-gig --skill code-audit-fmbp1981-hash
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-audit
Source: https://github.com/fmbp1981-hash/cavendish-gig/tree/main/.claude/plugins/intellix-plugin/skills/code-audit
Command: npx skills add https://github.com/fmbp1981-hash/cavendish-gig --skill code-audit-fmbp1981-hash

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill solves the problem of assessing and improving existing system codebases that require audit, refactoring, reorganization, or standardization to meet IntelliX clean architecture standards.

Core Features & Use Cases

  • Audit System Codebases: Conducts a thorough audit of existing systems against IntelliX clean architecture standards.
  • Identify Gaps and Generate Roadmap: Diagnoses gaps and produces a prioritized roadmap for refactoring and improving codebase.
  • Use Cases: Suitable for existing projects requiring structural improvement, refactoring legacy systems, or adhering to a clean architecture.

Quick Start

Run 'intellix:code-audit' to begin the code audit for your project.

Frequently Asked Questions about code-audit

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

FAQPage Schema
How do I audit an existing codebase against clean architecture standards?▼

To audit an existing codebase against clean architecture standards, run 'intellix:code-audit' to evaluate system structure and quality. It generates detailed reports and prioritized action plans for refactoring legacy systems.

What is the best way to identify technical debt and plan legacy system refactoring?▼

The best way to identify technical debt and plan legacy system refactoring is by conducting a thorough code audit. This evaluates existing structure against clean architecture standards and produces a prioritized improvement roadmap.

Can I use code audit techniques for reorganizing an existing project to meet clean architecture?▼

Yes, you can use code audit techniques for reorganizing existing projects to meet clean architecture standards. The audit diagnoses structural gaps and generates a targeted action plan for system reevaluation and standardization.

Do I need any specific dependencies to perform a system code review for technical debt?▼

No specific dependencies are required to perform a system code review for technical debt. The code audit operates independently to evaluate codebase quality and generate improvement roadmaps without external tool integrations.

What limitations should I consider when evaluating code structure for clean architecture compliance?▼

When evaluating code structure for clean architecture compliance, consider that the audit focuses on diagnostic reports and action plans rather than automated code modifications. It guides manual refactoring efforts for legacy system improvement.

Related Skills

Explore More Software Engineering Skills→
loianeloiane
50

brownfield-onboarding

Onboard an existing Spring codebase into a spec-driven workflow with baseline and design doc.

Community
Advanced
FelipePepeFelipePepe

rule-clean-code

Enforce clean-code standards during feature implementation, refactoring, and code reviews.

Community
Advanced
MathiasPaulenkoMathiasPaulenko

sonarqube-quality-gates

Enforce SonarQube quality gates and static analysis in CI/CD pipelines.

Community
Advanced
CassiiopeiaCassiiopeia
7

pro-refactor-analyze

Detect code smells and generate refactoring plans without modifying source code.

Community
Advanced