fp-update-spec

Update E2E_TESTS.md specifications from git history and source code changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automatically updates your E2E_TESTS.md files to reflect changes in your codebase, ensuring your end-to-end tests remain accurate and relevant without manual effort.

Core Features & Use Cases

  • Automated Spec Updates: Analyzes git history and source code to identify new, changed, or removed features.
  • Drafts Changes: Generates a clear summary of proposed modifications to your E2E_TESTS.md.
  • Use Case: After adding a new command-line argument to your application, run this Skill to automatically update the relevant feature description and assertions in your E2E_TESTS.md file.

Quick Start

Use the fp-update-spec skill to update the E2E_TESTS.md file in the current directory.

Frequently Asked Questions about fp-update-spec

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

FAQPage Schema
How do I automatically update E2E test specifications after code changes?

You can update E2E test specifications by analyzing git history and source code changes to automatically generate proposed modifications reflecting new, changed, or removed features in your E2E_TESTS.md file.

What is the best way to keep E2E specs in sync with source code?

The best way to keep E2E specs in sync is by analyzing git history and source code differences to detect behavioral changes, then drafting clear summaries to update your E2E_TESTS.md specification accurately.

Does updating E2E_TESTS.md require git log analysis?

Yes, updating E2E_TESTS.md requires git log analysis and source code comparison to comprehensively evaluate new features, changed behavior, and removed functionality for maintaining specification accuracy.

How do I maintain E2E test documentation when features are removed?

To maintain E2E test documentation when features are removed, the Skill evaluates git history to detect deleted functionality and drafts corresponding modifications to ensure your E2E_TESTS.md specification remains accurate.

Can I automate code maintenance for end-to-end testing specs?

Yes, you can automate code maintenance for end-to-end testing specs by running this Skill to analyze source code and git history, automatically drafting updates to the E2E_TESTS.md file without manual effort.