ada-code-quality-analysis

Audits source code across seven quality dimensions and generates evidence-backed markdown reports.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/wubing7755/Ada --skill ada-code-quality-analysis-wubing7755
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ada-code-quality-analysis
Source: https://github.com/wubing7755/Ada/tree/main/skills/software-development/ada-code-quality-analysis
Command: npx skills add https://github.com/wubing7755/Ada --skill ada-code-quality-analysis-wubing7755

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams need objective, evidence-based assessments of code health before refactors or releases, but manual audits are slow and findings are often unverifiable. This Skill automates multi-dimension static analysis and produces a structured report where every issue is traceable to a specific file and line. ## Core Features & Use Cases - Seven-dimension audit: Analyzes complexity, duplication, dead code, security risks, dependencies, test coverage, and code standards using automated Python scans plus manual reading of hot spots. - Structured reporting: Generates a markdown report with A-F grades per dimension, severity-rated findings (P0-P3), and verified per-directory statistics. - Independent verification: Dispatches three parallel sub-agents to cross-check the report for fabricated findings, missed security issues, and statistical inconsistencies. - Use Case: Before a major refactor, run a baseline audit of your src directory to identify high-complexity methods, duplicated blocks, untested critical files, and hardcoded secrets, then get a prioritized remediation plan. ## Quick Start Ask the agent to run a code quality analysis on your src directory covering complexity, duplication, security, and test coverage, and output the report to docs/reports/code-quality-YYYY-MM-DD.md.

Frequently Asked Questions about ada-code-quality-analysis

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

FAQPage Schema
How do I run a code quality audit on my source code?

Point the agent at your source directory and specify the dimensions you care about, such as complexity, duplication, or security. It runs automated Python scans first, then manually reads high-risk hot spots, and produces a markdown report with severity ratings and file:line evidence.

What does a static analysis report for code quality include?

The report includes an overall A-F grade, per-dimension sections for complexity, duplication, dead code, security, dependencies, test coverage, and standards, plus a P0-P3 prioritized improvement list. Appendices contain verified per-directory statistics and a verification record.

Which languages does this code quality analysis support?

The reference implementation targets C# with regex-based method extraction and xUnit test detection, but the patterns can be adapted for TypeScript, Python, and other languages. Generated directories like obj, bin, and node_modules are always excluded.

How are false positives in static analysis findings handled?

Every Critical and High finding must be verified by reading the actual source code before inclusion. Three parallel verification agents then sample findings for truthfulness, rescan all file types for missed security issues, and check statistical consistency.

When should I not use a full code quality audit?

Skip it for single-file reviews, efficiency-only audits, pre-commit checks, or simple line-count queries, which have dedicated lighter-weight skills. It is designed for multi-dimension assessments of whole source trees, not quick spot checks.