一键在 Manus 中运行任何 Skill

e2e-test-maker

星标29

分支9

更新时间2026年5月11日 19:01

Create, repair, and review Gardens V2 Playwright/Synpress E2E tests in pkg/e2e. Use when adding E2E scenarios, stabilizing flaky E2E CI, deciding UI-vs-RPC setup boundaries, adding Playwright projects, using MetaMask helpers, or updating the E2E GitHub Actions workflow.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

1Hive

1Hive/gardens-v2

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Gardens E2E Test Maker

When To Use

Use this skill for Gardens V2 end-to-end work in pkg/e2e, especially:

Adding or repairing Playwright/Synpress tests.
Debugging E2E CI flakiness, retries, Vercel preview selection, or PLAYWRIGHT_BASE_URL issues.
Deciding which parts of a flow should be prepared with RPC/subgraph and which parts must be exercised through the UI.
Adding a new test project to pkg/e2e/playwright.config.ts.
Working with MetaMask confirmation, visible-only locators, token minting/funding, pool archive cleanup, or proposal lifecycle tests.

If the task is primarily GitHub Actions failure triage, also use the GitHub gh-fix-ci skill. If the task requires live Gardens data or contract state, combine this skill with query-subgraph, read-contracts, or write-contract as appropriate.

Workflow

Read references/e2e-patterns.md before changing tests. It contains the current project layout, helper inventory, CI behavior, and scenario patterns.
Inspect the relevant current source files with rg, sed, and package-local scripts. Prefer existing helpers in pkg/e2e/tests/utils/ before adding new ones.
Use the UI for the behavior under test. Use RPC/subgraph only to make prerequisite state deterministic or to verify final state.
Keep Playwright projects serial and dependency ordered. If adding a scenario, wire it into pkg/e2e/playwright.config.ts in the intended lifecycle position.
Validate narrowly first with the target project, then run the dependent flow when credentials and network access are available.

Validation Commands

From pkg/e2e:

CI=true PLAYWRIGHT_BASE_URL="https://preview.example" pnpm exec playwright test tests/<test>.e2e.ts --project=<project-name>

For local UI:

PLAYWRIGHT_BASE_URL="http://localhost:3000" pnpm exec playwright test tests/<test>.e2e.ts --project=<project-name>

Use PLAYWRIGHT_BASE_URL; E2E_BASE_URL is not read by the Playwright config.

同仓库更多 Skills

同仓库

write-contract

1Hive/gardens-v2

Prepare Gardens V2 state-changing contract transactions. Use this skill when the task involves encoding calldata, selecting the correct deployed Gardens contract and ABI, building multisig payloads, or preparing a write transaction for manual execution or broadcast.

2026-06-0329

proposal-creator

1Hive/gardens-v2

Prepare Gardens proposal creation transactions in gardens-v2. Use for funding proposals, streaming proposals, signaling proposals, calldata preparation, signer readiness checks, IPFS metadata, Allo registerRecipient flows, covenant and pool description ingestion, missing-input extraction, and Foundry keystore execution review.

2026-04-1029

query-subgraph

1Hive/gardens-v2

Retrieve Gardens V2 indexed data by running direct GraphQL queries against the Gardens V2 subgraph endpoints. Use this skill when an external agent needs to answer Gardens questions, inspect entities, fetch on-chain indexed state, or choose the correct Gardens V2 dev endpoint for a specific network without relying on local repository access or writing application code.

2026-03-0429

read-contracts

1Hive/gardens-v2

Retrieve Gardens V2 on-chain state by reading deployed contracts with known ABIs and chain-specific addresses. Use this skill when an external agent needs to look up Gardens contract addresses, choose the correct ABI, inspect read-only contract state, or answer protocol questions directly from contract calls instead of writing code.

2026-03-0429

name	e2e-test-maker
description	Create, repair, and review Gardens V2 Playwright/Synpress E2E tests in pkg/e2e. Use when adding E2E scenarios, stabilizing flaky E2E CI, deciding UI-vs-RPC setup boundaries, adding Playwright projects, using MetaMask helpers, or updating the E2E GitHub Actions workflow.

Gardens E2E Test Maker

When To Use

Use this skill for Gardens V2 end-to-end work in pkg/e2e, especially:

Adding or repairing Playwright/Synpress tests.
Debugging E2E CI flakiness, retries, Vercel preview selection, or PLAYWRIGHT_BASE_URL issues.
Deciding which parts of a flow should be prepared with RPC/subgraph and which parts must be exercised through the UI.
Adding a new test project to pkg/e2e/playwright.config.ts.
Working with MetaMask confirmation, visible-only locators, token minting/funding, pool archive cleanup, or proposal lifecycle tests.

Workflow

Read references/e2e-patterns.md before changing tests. It contains the current project layout, helper inventory, CI behavior, and scenario patterns.
Inspect the relevant current source files with rg, sed, and package-local scripts. Prefer existing helpers in pkg/e2e/tests/utils/ before adding new ones.
Use the UI for the behavior under test. Use RPC/subgraph only to make prerequisite state deterministic or to verify final state.
Keep Playwright projects serial and dependency ordered. If adding a scenario, wire it into pkg/e2e/playwright.config.ts in the intended lifecycle position.
Validate narrowly first with the target project, then run the dependent flow when credentials and network access are available.

Validation Commands

From pkg/e2e:

CI=true PLAYWRIGHT_BASE_URL="https://preview.example" pnpm exec playwright test tests/<test>.e2e.ts --project=<project-name>

For local UI:

PLAYWRIGHT_BASE_URL="http://localhost:3000" pnpm exec playwright test tests/<test>.e2e.ts --project=<project-name>

Use PLAYWRIGHT_BASE_URL; E2E_BASE_URL is not read by the Playwright config.