agentleFS
Sign inStart free
AsiaOstrichAsiaOstrich/EngramGraph/.agents/skills/e2e-assistant/SKILL.md

e2e

Skill4 starsChanged 29 days agoMITView on GitHub

[UDS] Generate E2E test skeletons from BDD .feature scenarios, with framework detection and coverage gap analysis. Use when: turning finished .feature scenarios into runnable E2E skeletons, detecting the project E2E framework, finding AC with no E2E coverage. Not for: multi-story journeys with shared state — use the journey-test skill; writing the .feature scenarios themselves — use /bdd. Keywords: E2E, end-to-end test, feature file, test skeleton, framework detection, 端對端測試, 測試骨架, 場景轉測試.

50 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use instinct-export, instinct-import and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • TheKREATORSSkill

    instinct-export

    Export instincts from project/global scope to a file

    Also in 3 projects that use this

  • TheKREATORSSkill

    instinct-import

    Import instincts from file or URL into project/global scope

    Also in 3 projects that use this

  • diego-tobalinaSkill

    build-fix

    Fix build and compilation errors systematically. Run when build fails.

    Also in 4 projects that use this

  • 0mlkrizzz655335vSkill

    sdk

    Codex SDK 集成开发。用 TypeScript/Python SDK 做 agent 生命周期、流式输出、本地/云端执行等集成。

    Also in 3 projects that use this

  • MontimageSkill

    test-coverage

    Improve test coverage by finding untested branches, error paths, and edge cases. Use when measuring or strengthening a project's tests. Don't use for production debugging, code review, or feature implementation.

    Also in 3 projects that use this

  • MicrosoftSkill

    worktree

    Create, reuse or clean up a dedicated git worktree for working on a pull request or a private branch. Use from any PR-scoped workflow that needs an isolated checkout to keep current code and build output untouched.

    Also in 5 projects that use this

  • +1 more from TheKREATORS

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 44 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    After /e2e completes, the AI assistant should suggest:

    line 91

“Common” is measured: kept by at least 6 in 10 of the 44 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

E2E Assistant | E2E 助手

[!WARNING] Experimental Feature / 實驗性功能

This feature is under active development and may change significantly in v4.0. 此功能正在積極開發中，可能在 v4.0 中有重大變更。

Generate E2E test skeletons from BDD .feature scenarios, with framework detection and coverage gap analysis.

從 BDD .feature 場景生成 E2E 測試骨架，支援框架偵測與覆蓋差距分析。

Workflow | 工作流程

/derive bdd → .feature 場景
    ↓
/e2e → 分析 AC 適用性 → 偵測框架 → 參考既有模式 → 生成骨架
    ↓
手動執行驗證

Modes | 模式

1. Generation Mode (Default) | 生成模式（預設）

Analyze BDD scenarios, classify AC suitability, detect framework, and generate E2E test skeletons.

分析 BDD 場景、分類 AC 適用性、偵測框架、生成 E2E 測試骨架。

2. Analysis Mode (--analyze) | 分析模式

Scan coverage gaps between BDD features and existing E2E tests.

掃描 BDD feature 與既有 E2E 測試之間的覆蓋差距。

AC Classification | AC 分類

CategoryConditionExample
e2e-suitableMulti-step user flow or UI interactionLogin → Action → Verify
integration-suitableCross-component without UIAPI call → DB write
unit-suitablePure logic or computationSort, validate, format

Supported Frameworks | 支援框架

EcosystemFrameworkAuto-detectedDetection signal
JavaScriptPlaywright✅@playwright/test in package.json
JavaScriptCypress✅cypress dep + config file
JavaScriptVitest✅vitest dep + e2e directory
JavaScriptWebdriverIO❌ Manuallisted in SUPPORTED_FRAMEWORKS
Pythonpytest-playwright✅pytest-playwright in requirements
PythonSelenium + pytest✅selenium in requirements
PythonRobot Framework✅robotframework in requirements
PythonBehave✅behave in requirements
Gochromedp✅chromedp in go.mod
Gorod✅rod in go.mod
JavaSelenium WebDriver✅selenium-java in pom.xml / build.gradle
JavaPlaywright for Java✅playwright in pom.xml / build.gradle
JavaGauge✅gauge-java in pom.xml / build.gradle
RubyCapybara✅capybara in Gemfile
RubyWatir✅watir in Gemfile
C#Playwright for .NET❌ Manualnot yet auto-detected
C#Selenium WebDriver❌ Manualnot yet auto-detected

Usage | 使用方式

/e2e <feature-file>            - Generate E2E skeleton from BDD scenarios
/e2e <spec-file>               - Delegate to /derive e2e for SDD specs
/e2e --analyze                 - Scan all features for E2E coverage gaps
/e2e --analyze <feature-file>  - Analyze specific feature's AC suitability

Next Steps Guidance | 下一步引導

After /e2e completes, the AI assistant should suggest:

E2E 骨架已生成。建議下一步 / E2E skeleton generated. Suggested next steps:

  • 執行 /tdd 填入 [TODO] 標記的測試實作 ⭐ Recommended / 推薦 — Implement test logic
  • 執行 /checkin 品質關卡（若功能完成）— Quality gates (if feature complete)
  • 執行 /e2e --analyze 檢查整體 E2E 覆蓋狀況 — Check overall E2E coverage

Reference | 參考

  • Spec: SPEC-E2E-001
  • Core standard: testing-standards.md
  • Utilities: cli/src/utils/e2e-analyzer.js, cli/src/utils/e2e-detector.js

AI Agent Behavior | AI 代理行為

完整的 AI 行為定義請參閱對應的命令文件：/e2e

For complete AI agent behavior definition, see the corresponding command file: /e2e

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free