E2E Coverage Check
SkillDev toolsAnalyze 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.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the E2E Coverage Check skill
What this skill tells your AI
The instructions your AI receives, as published by incubateur-ademe/benefriches in .claude/skills/e2e-coverage-check/SKILL.md and read by ahel’s review.
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
-
Launch the
e2e-coverage-checkeragent 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.
-
Relay the agent's report to the user exactly as produced. Do not summarize or modify it.
Signals
- GitHub stars
- 45
- Forks
- 3
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
e2e-coverage-check- Source
- github.com/incubateur-ademe/benefriches