One-click install
npx skills add https://github.com/AlexCMarty/CUNYAutoLogin --skill test-coverage-audit-alexcmarty
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-coverage-audit
Source: https://github.com/AlexCMarty/CUNYAutoLogin/tree/main/.claude/skills/test-coverage-audit
Command: npx skills add https://github.com/AlexCMarty/CUNYAutoLogin --skill test-coverage-audit-alexcmarty

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the guesswork of identifying weak, missing, or implementation-bound tests in your codebase, especially for high-risk security and credential-related paths, so you can prioritize test improvements with confidence instead of chasing arbitrary coverage numbers.

Core Features & Use Cases

  • Behavior-First Auditing: Judges tests by whether they pin observable user behavior rather than implementation details, flagging tests that break on safe refactors.
  • Risk-Weighted Prioritization: Ranks coverage gaps by blast radius, so security, crypto, and credential paths outrank cosmetic test gaps.
  • Structured Audit Output: Produces a single, parseable audit file that serves as the contract for the paired act-on-test-audit skill to fill identified gaps.
  • Use Case: For a browser extension handling user credentials like CUNYAutoLogin, it will flag untested credential encryption paths and tests that assert on internal mock calls before any test refactor, preventing security regressions.

Quick Start

Invoke the test-coverage-audit skill to generate a risk-ranked report of your test suite's weak spots before making any test changes.

Frequently Asked Questions about test-coverage-audit

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

FAQPage Schema
How do I audit test coverage gaps by risk instead of arbitrary coverage percentages?▼

Implementation-bound tests assert on internal mock calls or implementation details rather than observable user behavior, causing safe refactors to break. A behavior-focused audit flags these brittle tests before you refactor.

Can I audit my test suite for security regressions without writing new tests?▼

A test coverage audit synthesizes parallel domain-specific inspections into a single structured audit file, ranking untested behavior and implementation-bound tests by risk to produce an evidence-based improvement contract.

Does the test coverage audit work with both unit and E2E test infrastructure?▼

Implementation-bound tests assert on internal mock calls or implementation details rather than observable user behavior, causing safe refactors to break. A behavior-focused audit flags these brittle tests before you refactor.

How do I identify implementation-bound tests that break during safe refactoring?▼

Implementation-bound tests assert on internal mock calls or implementation details rather than observable user behavior, causing safe refactors to break. A behavior-focused audit flags these brittle tests before you refactor.

What is risk-weighted test prioritization and when do I need it?▼

Risk-weighted test prioritization ranks coverage gaps by blast radius so security, crypto, and credential paths outrank cosmetic gaps. You need it when evidence-based test improvement matters more than chasing coverage numbers.