fp-audit

Analyze gaps between E2E test specifications and implemented test cases.

6|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/endorhq/flightplanner --skill fp-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fp-audit
Source: https://github.com/endorhq/flightplanner/tree/main/skills/fp-audit
Command: npx skills add https://github.com/endorhq/flightplanner --skill fp-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies gaps between your End-to-End (E2E) test specifications and your actual test implementations, ensuring your tests accurately reflect your project's intended behavior.

Core Features & Use Cases

  • Specification Analysis: Parses E2E_TESTS.md files to understand desired features, suites, and categories.
  • Test Code Analysis: Scans test files (*.e2e.test.*, **/e2e/**/*.test.*) to identify suites, test cases, and skip markers.
  • Coverage Matrix Generation: Creates a detailed report showing which spec features are covered, missing, stale, or skipped by existing tests.
  • Use Case: After updating your E2E_TESTS.md to include new user flows, run fp-audit to quickly see which new tests need to be written and which existing tests might be outdated.

Quick Start

Run fp-audit to analyze the gap between E2E specifications and existing test implementations.

Frequently Asked Questions about fp-audit

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

FAQPage Schema
How do I find missing E2E tests in my project?

To find missing E2E tests, fp-audit parses markdown specification files like E2E_TESTS.md and scans your test codebase to generate a coverage matrix highlighting missing, stale, or skipped test cases.

What is E2E test specification auditing?

E2E test specification auditing analyzes the discrepancy between desired features documented in E2E_TESTS.md files and actual implemented test cases to identify gaps and structural issues within test suites.

How do I check coverage for skipped E2E test cases?

You can check coverage for skipped E2E test cases by scanning test files matching patterns like *.e2e.test.* for skip markers and mapping them against your specification categories to report overall per-category coverage.

Does fp-audit work with existing markdown test specifications?

Yes, fp-audit works with existing markdown test specifications by parsing E2E_TESTS.md files to understand desired features, suites, and categories, then comparing them against your implemented test codebase.

What is the best way to track outdated E2E tests?

The best way to track outdated E2E tests is running fp-audit to scan test files for stale cases, generating a detailed coverage matrix that reports which spec features are covered, missing, or skipped.