ln-632-test-e2e-priority-auditor

Audit E2E test coverage for critical paths and core user journeys.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/cbbkrd-tech/jl-finishes --skill ln-632-test-e2e-priority-auditor-cbbkrd-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-632-test-e2e-priority-auditor
Source: https://github.com/cbbkrd-tech/jl-finishes/tree/main/.claude/skills/ln-632-test-e2e-priority-auditor
Command: npx skills add https://github.com/cbbkrd-tech/jl-finishes --skill ln-632-test-e2e-priority-auditor-cbbkrd-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the auditing of End-to-End (E2E) test coverage for critical application paths, ensuring that high-priority functionalities like payment processing and security are adequately tested and identifying wasteful E2E tests.

Core Features & Use Cases

  • Critical Path Auditing: Validates E2E test coverage for high-priority areas (Money, Security, Data).
  • User Journey Validation: Ensures core multi-step user flows have corresponding E2E tests.
  • Wasteful Test Identification: Flags E2E tests with low usefulness scores that could be optimized.
  • Use Case: A Quality Assurance lead can use this Skill to quickly assess the E2E test suite's effectiveness against business-critical features, receiving a clear report on gaps and inefficiencies.

Quick Start

Run the ln-632-test-e2e-priority-auditor skill to audit E2E critical coverage for the project.

Frequently Asked Questions about ln-632-test-e2e-priority-auditor

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

FAQPage Schema
How do I audit E2E test coverage for critical application paths?

E2E critical path auditing validates test coverage for high-priority business areas like payment processing and security. It works by parsing application context, identifying critical paths, checking for existing E2E tests, and calculating a compliance score to highlight coverage gaps.

How do I identify wasteful E2E tests in my test suite?

Identifying wasteful E2E tests involves flagging tests with a low usefulness score, specifically those scoring below 15. This Skill automates the identification process by evaluating your E2E suite against this threshold, allowing you to optimize or remove inefficient tests.

What is risk-based testing for core user journeys?

Risk-based testing for core user journeys prioritizes validating multi-step user flows based on business impact. This Skill implements risk-based testing by ensuring E2E tests exist for journeys with a priority score between 15 and 19, aligning test execution with business criticality.

Can I validate E2E tests for payment processing and security without external dependencies?

You can validate E2E tests for payment processing and security without external dependencies. This Skill operates independently to parse your application context, identify critical paths related to Money and Security, and verify E2E test existence to generate a compliance report.

What are the limitations of automated E2E test auditing?

Automated E2E test auditing is limited by its reliance on accurate context parsing and predefined priority scores. It should not be used as the sole quality gate if your application paths lack explicit business impact classifications for Money, Security, and Data, as the compliance score depends on these inputs.