Validate E2E_TESTS.md structure, metadata, and quality without modifying files.
npx skills add https://github.com/endorhq/flightplanner --skill fp-review-spec
Please help me install this Agent Skill. Skill: fp-review-spec Source: https://github.com/endorhq/flightplanner/tree/main/skills/fp-review-spec Command: npx skills add https://github.com/endorhq/flightplanner --skill fp-review-spec
This Skill addresses the challenge of maintaining high-quality, consistent End-to-End (E2E) test specifications by automating their validation. It ensures that E2E_TESTS.md files are comprehensive, well-structured, and adhere to defined standards, preventing errors and improving the reliability of AI-generated tests.
<!-- category: ... -->, <!-- skip: ... -->) are present and use valid values.Run the fp-review-spec skill to validate all E2E_TESTS.md files in the current project.
High-intent search queries and answers about installing and using this skill.
To validate E2E test specification structure, check the E2E_TESTS.md file for required sections like Index, Suites, Preconditions, Features, and Postconditions. This ensures AI agents can reliably parse and generate tests from well-formed markdown documentation.
Declarative writing style validation for E2E test documentation checks for vague assertions and incorrect tense usage in E2E_TESTS.md files. It reports quality issues without modifying files, ensuring test specifications remain clear and actionable for automated generation.
To verify metadata comments in markdown test specifications, scan E2E_TESTS.md files for required tags like <!-- category: ... --> and <!-- skip: ... -->. This process ensures metadata values are present and valid for proper test automation workflow configuration.
You can check for missing error categories in E2E test suites by analyzing feature category coverage within E2E_TESTS.md files. This analysis provides warnings for missing critical categories like 'error' and informational notes for optional ones, ensuring comprehensive test coverage.
Validating E2E test specs does not modify your original markdown files. The validation process strictly reports findings regarding structure, metadata, and quality issues in E2E_TESTS.md files, ensuring your test documentation remains untouched during the review process.
Common quality issues in E2E test specifications include duplicate feature names, non-achievable preconditions, vague assertions, and incorrect tense usage. Identifying these issues ensures comprehensive and well-formed E2E test documentation for reliable AI agent workflow execution.
naviktReview repository README structure and scaffold drafts with placeholders.
NVIDIAValidate and compare Spark UDF implementations across CPU and GPU paths.
auldsyababuaValidate Markdown files for syntax, links, and formatting standards.
polseguValidate YAML frontmatter, phase structure, and procedural hints in SKILL.md files.