菜单
Land an E2E spec for an unshipped feature behind a feature flag — spec is committed but skipped in CI until the flag is flipped. Invoke when writing tests-first for a feature that isn't implemented yet, or when an existing flag needs to flip from false to true on shipping.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Register a project-local assertion type (the `x-` prefix family) when the 8 built-ins (exit_code, contains, not_contains, stderr_contains, regex, json_path, count, golden_file) cannot express the check. Invoke only when a built-in genuinely doesn't fit.
Author one YAML spec under tests/e2e/specs/<wave>/ that exercises a daemon/server/long-running process — with readiness polling, clean-shutdown verification, and optional log assertions. Invoke when the user asks to "write an e2e test for the server", "spec the daemon", "test the watch subcommand", "verify graceful shutdown", or any test that needs a process running in the background while other steps run.
Author one YAML spec under tests/e2e/specs/<wave>/ for one CLI feature, with appropriate assertions and an auto-rendered sidecar notes file. Invoke when the user asks to "write an e2e test for X", "add a spec for the Y subcommand", or to verify a CLI feature end-to-end.
One-shot setup of the gotit E2E test suite in a Go CLI project — wires runner_test.go, features.yaml, AGENTS.md, .gitignore, and a passing smoke spec. Invoke when the user asks to "add e2e tests", "set up gotit", or "scaffold end-to-end tests" in a Go project.
Read the most recent JSONL log under tests/e2e/results/, identify the failed step, classify the failure, and propose a fix or open a tracking issue. Invoke when a test fails locally or in CI and the user wants to debug it.
Convert an existing CLI test suite (bats, expect, pytest+subprocess, Makefile-driven shell scripts) into gotit YAML specs. Invoke when the user is migrating an established test suite to gotit.
| name | gotit-add-feature-flag |
| description | Land an E2E spec for an unshipped feature behind a feature flag — spec is committed but skipped in CI until the flag is flipped. Invoke when writing tests-first for a feature that isn't implemented yet, or when an existing flag needs to flip from false to true on shipping. |
| version | 1 |
Use feature flags to land specs ahead of the implementation. The spec is real, runnable, and ships with the PR; CI just skips it until the flag flips.
Do not gate specs that should pass today. The flag system is for unshipped features, not for flaky tests — flaky tests get fixed or deleted.
Pick a flag name in kebab-case, descriptive of the feature: rename-detection, multi-tenant-config, progressive-streaming. Avoid generic names (new-feature, wip).
Add the flag to tests/e2e/features.yaml with false:
enabled:
rename-detection: false # #123 detect renames across commits
Add a comment with a tracking link (issue number, PR, ticket) so future-you knows what the flag is gating.
Gate the spec with requires: [feature:<name>]:
spec_version: 1
name: rename-detection-basic
requires: [feature:rename-detection]
repo:
helper: two-commit-rename
steps:
- …
Verify the spec is skipped by default:
go test ./tests/e2e/ -run "TestE2E/<wave>/<spec>" -v
Expect --- SKIP with the message about the flag not being shipped.
Verify the spec runs when forced on:
<PREFIX>_E2E_FEATURES=rename-detection go test ./tests/e2e/ -run "TestE2E/<wave>/<spec>" -v
Substitute <PREFIX> with the project's EnvPrefix. The spec should now run (and may fail if the feature isn't implemented — that's expected).
When shipping the feature, flip the flag in the same PR that lands the implementation:
enabled:
rename-detection: true
The spec activates automatically on the next CI run; no spec edits needed.
rename-detection-1, rename-detection-2.all sentinel in the env override turns on every flag listed in the file: <PREFIX>_E2E_FEATURES=all. Use locally to see what's currently failing; never ship a CI run with =all.false (skip). It's safe to commit a spec referencing a flag that doesn't exist yet — but that obscures intent. Add the false line to features.yaml in the same commit.