coverage-booster

1.8k
openclawopenclaw

Find untested code paths and generate tests to boost coverage. Use when your test coverage is too low and you need to fill the gaps.

194 days ago

analyzing-test-coverage

1.5k
jeremylongshorejeremylongshore

This skill analyzes code coverage metrics to identify untested code and generate comprehensive coverage reports. It is triggered when the user requests analysis of code coverage, identification of coverage gaps, or generation of coverage reports. The skill is best used to improve code quality by ensuring adequate test coverage and identifying areas for improvement. Use trigger terms like "analyze coverage", "code coverage report", "untested code", or the shortcut "cov".

194 days ago

crap-analysis

445
AarononthewebAaronontheweb

Analyze code coverage and CRAP (Change Risk Anti-Patterns) scores to identify high-risk code. Use OpenCover format with ReportGenerator for Risk Hotspots showing cyclomatic complexity and untested code paths.

194 days ago

test-coverage

241
MadAppGangMadAppGang

On-demand test coverage analysis. Use when identifying untested code, finding test gaps, measuring coverage metrics, or improving test quality. Trigger keywords - "test coverage", "coverage report", "untested code", "test gaps", "missing tests", "coverage metrics".

devtestingcoverage+2
194 days ago

ln-634-test-coverage-auditor

131
levnikolaevichlevnikolaevich

Coverage Gaps audit worker (L3). Identifies missing tests for critical paths (Money 20+, Security 20+, Data Integrity 15+, Core Flows 15+). Returns list of untested critical business logic with priority justification.

194 days ago

legacy-code-safety

98
TheBushidoCollectiveTheBushidoCollective

Use when modifying, removing, or refactoring code that lacks test coverage. Emphasizes the danger of untested changes and the RGR workflow to add characterization tests before modifications.

194 days ago

Test Coverage Gap Finder

71
PramodDuttaPramodDutta

Identify untested code paths, uncovered branches, and missing test scenarios using coverage analysis, risk mapping, and change-based coverage tracking

test-coveragecode-coveragebranch-coverage+4
194 days ago

test-gap-analyzer

28
rysweetrysweet

Analyzes code to identify untested functions, low coverage areas, and missing edge cases. Use when reviewing test coverage or planning test improvements. Generates specific test suggestions with example templates following amplihack's testing pyramid (60% unit, 30% integration, 10% E2E). Can use coverage.py for Python projects.

194 days ago

traceability-auditor

25
nahisahonahisaho

Validates complete requirements traceability across EARS requirements → design → tasks → code → tests. Trigger terms: traceability, requirements coverage, coverage matrix, traceability matrix, requirement mapping, test coverage, EARS coverage, requirements tracking, traceability audit, gap detection, orphaned requirements, untested code, coverage validation, traceability analysis. Enforces Constitutional Article V (Traceability Mandate) with comprehensive validation: - Requirement → Design mapping (100% coverage) - Design → Task mapping - Task → Code implementation mapping - Code → Test mapping (100% coverage) - Gap detection (orphaned requirements, untested code) - Coverage percentage reporting - Traceability matrix generation Use when: user needs traceability validation, coverage analysis, gap detection, or requirements tracking across the full development lifecycle.

194 days ago

test-coverage-analyzer

25
armanzeroeightarmanzeroeight

Analyzes test coverage reports, identifies gaps, and recommends priority areas for testing. Use when reviewing coverage, finding untested code, or planning test improvements.

194 days ago

Test Coverage Guardian

20
sunholo-datasunholo-data

Analyze test coverage, identify gaps, detect dead code, and improve test quality. Use when user asks to check coverage, review tests, find untested code, or improve test robustness.

194 days ago

coverage-analyzer

19
matteocervellimatteocervelli

Analyze test coverage with detailed metrics, identify gaps, and generate comprehensive reports. Use when measuring code coverage, finding untested code, or validating coverage thresholds.

194 days ago

test-coverage

18
mehdicmehdic

Generate comprehensive test coverage reports when reviewing code. Identifies untested code paths and low-coverage areas. Supports Python (pytest-cov), JavaScript (jest), Go (go test -cover), Java (JaCoCo). Use when reviewing tests or before approving code changes.

194 days ago

quality-coverage-report

14
HomericIntelligenceHomericIntelligence

Generate test coverage reports showing which code paths are tested. Use to identify untested code and improve test coverage.

194 days ago

calculate-coverage

14
HomericIntelligenceHomericIntelligence

Measure test coverage and identify untested code. Use when assessing test completeness.

194 days ago

code-generate-tests

8
sirnsirn

Generate tests for untested functions and edge cases, then run them. Use when user asks to generate tests, add tests, or create test coverage.

194 days ago

refactoring

8
BumgeunSongBumgeunSong

Use when user explicitly asks to refactor code, or when test coverage is requested for untested code with side effects. Enforces Functional Core Imperative Shell pattern extraction before any changes.

194 days ago

analyzing-test-coverage

8
BbgnsurfTechBbgnsurfTech

Analyze code coverage metrics and identify untested code paths. Use when analyzing untested code or coverage gaps. Trigger with phrases like "analyze coverage", "check test coverage", or "find untested code".

194 days ago

CRAP Analysis

1
wshaddixwshaddix

Analyze code coverage and CRAP (Change Risk Anti-Patterns) scores to identify high-risk code. Use OpenCover-format coverage with ReportGenerator to produce Risk Hotspots that show cyclomatic complexity and untested code paths. Use this when evaluating code quality and test coverage before changes, when identifying high-risk code that needs refactoring or additional tests, when setting up coverage collection for a .NET project, or when establishing coverage thresholds for CI/CD pipelines.

194 days ago

test-writer

shellsage-aishellsage-ai

Generate unit and integration tests for existing code. Use when: adding test coverage, writing tests for untested code, or bootstrapping a test suite. NOT for: running tests, fixing failing tests, or debugging test infrastructure.

194 days ago

analyzing-test-coverage

nivkazdannivkazdan

Analyze code coverage metrics and identify untested code paths. Use when analyzing untested code or coverage gaps. Trigger with phrases like "analyze coverage", "check test coverage", or "find untested code".

194 days ago