ada-quality-report-qa

Validates code quality reports against statistical, coverage, and file-count errors before delivery.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Hand-written code quality reports contain roughly 10% errors in their first drafts: mismatched line-count totals, missed aggregated test files, header-versus-appendix file count contradictions, and double-counted subdirectories. This Skill adds four verification gates that catch these errors before a report reaches the user. ## Core Features & Use Cases - Statistical Formula Consistency: Cross-checks the sum of per-directory line counts against a single unified find ... | wc -l total, flagging any mismatch instead of trusting manual addition. - Aggregated Test File Detection: Uses grep -rhoP 'class\s+\w+Tests\b' to find test classes inside aggregated files (e.g., DomainModelTests.cs) that simple filename matching (FooTests.cs ↔ Foo.cs) misses. - Scope and Boundary Verification: Reconciles the report header's claimed file count with the appendix table, and separates top-level directory counts from subdirectory counts using find -maxdepth 1. - Use Case: After drafting a code quality report with an Appendix A file statistics table and test coverage data, run these four gates to confirm every number is reproducible from shell commands before delivering the report. ## Quick Start Ask the agent to run the four quality gates on the completed code quality report and fix any statistical or coverage discrepancies before delivery.

Frequently Asked Questions about ada-quality-report-qa

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

FAQPage Schema
How do I verify line counts in a code quality report?

Run a single unified find command piping all source files into wc -l to get the true total, then compare it against the sum of per-directory counts. Any mismatch between the two numbers indicates an error that must be fixed before delivery.

How to detect test coverage missed by filename matching?

Filename matching like FooTests.cs to Foo.cs misses aggregated test files containing multiple test classes. Extract all test class names with grep -rhoP 'class\s+\w+Tests\b' across test files, strip the Tests suffix, and match them against source class names.

Why does my report header file count not match the appendix?

Common causes include forgetting root-level files like _Imports.razor, or accidentally counting generated files like lib.js. Count source files independently with a find command excluding obj and bin directories, then reconcile both numbers.

When should I not use this QA gate skill?

Do not use it for running the initial static analysis or for verifying individual report claims, since those are earlier pipeline stages. It is the final QA gate applied after a code quality report is fully drafted and before delivery.

How do I avoid double-counting subdirectories in line statistics?

Use find with -maxdepth 1 for parent-only counts so files in child subdirectories are excluded, then list child subdirectories as separate rows. Verify the parent-only count plus child subtotals equals the full recursive count.