Analyze current branch changes vs main and determine whether e2e tests need to be created or updated. Produces a structured report with coverage gaps and recommendations. Use after completing a feature or before creating a PR.
Scanned 9/3/2026
Install to Claude Code
Skills Directorynpx -y skills add incubateur-ademe/benefriches --skill e2e-coverage-check --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of E2e Coverage Check?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/incubateur-ademe-e2e-coverage-check)More formats (shields.io, HTML) on the badges page.
---
name: e2e-coverage-check
description: >
Analyze current branch changes vs main and determine whether e2e tests need to be
created or updated. Produces a structured report with coverage gaps and recommendations.
Use after completing a feature or before creating a PR.
effort: medium
allowed-tools: Agent
user-invocable: true
---
# E2E Coverage Check
Analyze whether current branch changes require new or updated e2e tests.
## When to Use
- After completing a feature implementation, before creating a PR
- When changes touch views, wizard steps, routes, controllers, or shared DTOs
- To verify that new user-facing flows have adequate e2e test coverage
## Instructions
1. Launch the `e2e-coverage-checker` agent with this prompt:
> Analyze the current branch's changes against main and produce an e2e coverage check report. Follow your instructions step by step: collect the diff, classify files, run the deep pass where needed, map coverage, and generate the report.
2. Relay the agent's report to the user exactly as produced. Do not summarize or modify it.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Practical guide to testing web applications with screen readers for comprehensive accessibility validation.
Add a new Paperclip issue-thread interaction kind end-to-end. Use when repo work introduces or extends interaction cards like request_confirmation, checkbox confirmations, ask_user_questions, or suggest_tasks.
Run, verify, reseed, and repair Paperclip isolated dev workspace services. Use when asked to start or fix a managed project/worktree service and prove health, login readiness, cloned data, runtime visibility, and correct port ownership.
Plan a weekly editorial calendar by mapping company goals to publishable topics, owners, status, and verification notes.
Prepare a Paperclip branch for PR with commits, template body, and checks.
