harness-fixture-smoke-test
Skill1 starsChanged 2 months agoMITView on GitHub
Exercise the setup pipeline end to end against a disposable fixture repository outside this project, to prove that inspection, rendering, validation, and dry-run installation still work together. Invoke explicitly after changing templates, the renderer, the validator, or the installer.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- harness-orchestrationSkill
- harness-release-bumpSkill
- harness-sessionSkill
The file
Files
harness-fixture-smoke-test
- The unit suite covers the scripts in isolation. This procedure proves the pipeline composes. Never run it against a real project.
- Create a scratch fixture directory outside this repository. Never use the project root as a fixture target.
- For an
existingfixture, add a small but real shape: a manifest, a source directory, and a README. For anewfixture, leave it empty or add only a planning README.
- For an
- Run the inspector against the fixture and read
project_statefrom the JSON. Confirm it classifies the fixture the way you intended.
- Run the inspector against the fixture and read
- Start from a documented profile under
examples/rather than writing one from scratch, then adjust only the fields under test.
- Start from a documented profile under
- Render into a staging directory with
render_harness.py, then runvalidate_harness.pyagainst the output. Both must pass before you go further.
- Render into a staging directory with
- Run the generated
install-harness.sh --target <fixture> --dry-runfirst. Read the NEW / IDENTICAL / CONFLICT / BLOCKED classification and confirm it matches what you expect.
- Run the generated
- Run
--apply-new-only, then runcheck_installed.pyagainst the fixture.
- Run
- To exercise the conflict path, pre-create a file that the payload also provides, re-run the dry run, and confirm it is reported as CONFLICT and is not overwritten.
- Delete the fixture and the staging output when finished.
- Report what you actually observed at each step, including any step you could not complete on this platform.
User-supplied context:
$ARGUMENTS
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
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.

