Discover and document end-to-end workflows as Markdown e2e case specs.
npx skills add https://github.com/Vamdawn/ai-forge --skill e2e-find
Please help me install this Agent Skill. Skill: e2e-find Source: https://github.com/Vamdawn/ai-forge/tree/main/skills/e2e-find Command: npx skills add https://github.com/Vamdawn/ai-forge --skill e2e-find
This skill analyzes a codebase to automatically discover and document end-to-end workflows as Markdown e2e case specifications, reducing manual documentation effort and aligning tests with real code paths.
Analyze the repository to identify an e2e flow, start the service for entry validation, and generate or update a single stable e2e case file under the selected specs/e2e directory.
High-intent search queries and answers about installing and using this skill.
To generate e2e test specs from code analysis, you can dissect a codebase to discover user workflows and document them as Markdown case specifications. This process extracts entry routes, state transitions, and terminal assertions directly from the code paths.
Deduplicating end-to-end workflow documentation involves comparing newly discovered flows against existing cases to update or create files while preserving flow IDs and changelogs. This ensures a single stable file per workflow without redundant entries.
Documenting e2e workflows for a monorepo with multiple entry points requires analyzing the codebase to identify distinct service routes and critical state transitions. It generates a stable single-file workflow spec per flow under a selected directory.
Yes, you can validate e2e case specs against a running web service by starting the service for entry validation. The process determines identifiable entry routes and terminal assertions using service detection and code-driven validation checks.
An e2e case specification for automated testing should include identifiable entry routes, core goals, state transitions, terminal assertions, code anchors, API endpoint references, UI element references, and a Change Log to track iterative updates.
To preserve flow IDs when updating e2e test cases, compare new code analysis results against existing case files to update them iteratively. This deduplication process maintains a single stable file per flow while recording changes in a changelog.
queen-of-codeAnalyze a codebase and produce a read-only structural summary.
eventua11yAutomate E2E and unit test setup and execution with Playwright and Vitest.
jokken79Generate tests, detect flaky tests, and analyze coverage for Python projects.
okwindsTransform a PRD into an implementation-ready engineering specification with architecture, data modeling, API design, security, deployment, and testing.
