Clean-context tester handoff — forks omelette-tester with the approved spec and the diff taken from git at invocation, so the tester never receives the coder's summary. Usage: /omelette-test <spec path> [repo path]
Installs into .claude/skills of the current project.
Are you the author of Omelette Test?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/adxd-og-omelette-test)
---
{{marker}}
name: omelette-test
description: "Clean-context tester handoff — forks omelette-tester with the approved spec and the diff taken from git at invocation, so the tester never receives the coder's summary. Usage: /omelette-test <spec path> [repo path]"
context: fork
agent: omelette-tester
argument-hint: "[spec path] [repo path]"
---
Spec to test against: read `$0` first; it is the authority.
Repository under test: `$1` — when empty, the current directory.
Diff of the working tree, taken from git at invocation (uncommitted work included):
!`git -C "$1" diff HEAD`
Untracked files (read them by path if they are part of the change):
!`git -C "$1" ls-files --others --exclude-standard`
Now follow your procedure: list the behaviours the spec promises, check coverage, write additional tests in a NEW file, run them through the real runner, quote the raw output, and rule each failure test-vs-spec. Never edit the implementation or the implementer's tests.
