메뉴
Add a static repository fixture under tests/e2e/testdata/repos/ that specs reference via `repo.fixture:`. Invoke when a spec needs a small, file-tree-based test repo (no commit history beyond an initial commit).
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-fixture |
| description | Add a static repository fixture under tests/e2e/testdata/repos/ that specs reference via `repo.fixture:`. Invoke when a spec needs a small, file-tree-based test repo (no commit history beyond an initial commit). |
| version | 1 |
Create a static repository fixture for use as repo.fixture: <name> in specs.
gotit-add-helper): when commit history matters — renames, multi-file co-changes, branches, conflicts, time-stamped commits.If the test only cares about file contents at a single point in time, a fixture is the right answer.
Pick a name (kebab-case): describes the shape of the repo, not the test (e.g. multi-package, single-binary, monorepo-with-vendor).
Create the directory tests/e2e/testdata/repos/<name>/.
Add the files that the test repo should contain. The runner copies the tree as-is, then runs git init -b main, git add -A, git commit -m "initial fixture commit". So:
.git/ directory — the runner builds it..gitignore unless the test specifically needs to verify ignore behavior.Reference from a spec:
repo:
fixture: <name>
Verify: run any spec that uses the fixture to confirm it provisions correctly.