press
Run the tests-only adversarial pass after `/cook`. Report each defect as a finding for a Cook correction. Use this skill when the user says "press the changes", "harden this", "press before /age", or "/press". Do not edit production code.
How do I install this agent skill?
npx skills add https://github.com/paulnsorensen/easy-cheese --skill pressIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The 'press' skill implements a structured adversarial testing phase within a development pipeline. It uses local packaged Python commands to route workflow decisions and record telemetry. The skill includes strict constraints against modifying production code and follows a predefined JSON-based communication protocol between phases. No malicious patterns or unauthorized exfiltration methods were detected.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
/press
Press is the tests-only adversarial pass after /cook. It reports a GREEN pass to /age and a finding to Cook.
Press never owns first coverage. Press never edits production code. Cook owns the implementation. Press attacks the approved contract and reports each defect it exposes.
Phase entry
Run python3 skills/press/scripts/press.pyz wheypoint-resolve --ref <slug>.
authoritative uses the record; its working_context is the first batched tilth_read.
not-found proceeds cold; legacy shows its source and slug, then proceeds.
gated, ambiguous, and error stop and show the payload.
Show advisory stale-commit and grounded-path-missing findings.
Inputs
Press accepts this invocation:
/press <slug> [--auto] [--hard] [--open-pr]
After phase entry, Press reads .cheese/cook/<slug>.md for the Cook handoff.
--auto selects the autonomous chain. See ## Auto mode.
--hard requests the optional final gate. Press forwards this flag to Age.
--open-pr is publication permission. Only the user supplies it. Press forwards this flag to Age. Press never adds it.
Press preserves the Cook durable_flags: value without change. Press ignores the Cook taste_test: value.
Adversarial loop
- Attack — Add or run only tests, fixtures, and test-only harness support. Use the approved seam and witness. Keep the attack identity and test digest stable.
- Classify — Use
findingwhen an attack test exposes a defect. Usegreenfor a clean pass. Useproduction_changedwhen the attempt changed production paths. Useinvalid_evidencewhen you cannot verify the evidence. - Report — Report each finding with its failing test. Hand it to Cook as a correction.
- Replay — Replay the same attack after the correction returns. Use the same attack and test digest. Then classify the result again.
- Terminate — Hand off to
/ageafter GREEN.
Invalid evidence and a production tree change stop the run. A third finding on the same attack also stops the run. The outcome table defines the correction cap.
Press has no global dispatch: /cook action. A Cook correction runs only for a reported finding.
Baseline-aware gates
Press preserves baseline-aware readiness for project gates. The Cook baseline: line names one artifact. That artifact holds the settled state.
Read the artifact through the baseline: path. Do not re-flag a failure when its test and signature match the artifact. New or changed failures block the route.
See ../cook/references/quality-gates.md. Also see references/gap-analysis.md.
Flow
- Read — Load the approved spec, Cook handoff, and baseline block. Use canonical terms from
.cheese/glossary/<slug>.mdwhen that file exists. - Attack — Add or run only adversarial tests. Do not add first-coverage tests. Do not change production paths.
- Classify — Select
green,finding,invalid_evidence, orproduction_changedfrom the adversarial run. - Report — Write
.cheese/press/<slug>.md. Include the attempts, evidence, and review follow-ups. - Hand off — Send GREEN to
/age. Send a finding to Cook as a correction.
Use code-intelligence-routing.md for source changes.
Use ../cheese/references/harness-portability.md for portability.
The reference states that slash commands are host renderings, not the control model.
Press reports one readiness value. Map ready for /age to status: ok and next: age.
Map follow-up recommended to status: ok-with-concerns: <concern> and next: age. Use this status for a GREEN pass that also records a review follow-up. Age owns each recorded concern.
Map finding to status: ok-with-concerns: <defect> and next: cook.
Map blocked to status: halt: <reason> and next: done. blocked means invalid evidence or a production change. Stop after that status.
Auto mode
--auto runs the same adversarial loop. It also selects the next phase without a user prompt.
Dispatch /age <slug> --auto after ready for /age or follow-up recommended. Add --hard when the user supplied it. Add --open-pr when the user supplied it.
Stop after blocked or halt: correction-cap. Do not dispatch Age.
Honor the no-chain directive when the caller supplies it. Write the Press handoff and stop. Do not start another phase. Cook's fan pathway owns this directive. The retired /ultracook orchestrator previously owned it. Test for the directive itself. Do not test for the source name. See ../cook/references/auto-mode.md.
Output
Write .cheese/press/<slug>.md at each Press result.
Write the file with python3 skills/press/scripts/press.pyz write-handoff-artifact; include one or more --grounded <path[#start-end]> arguments. Use the canonical preamble:
python3 skills/press/scripts/press.pyz write-handoff-artifact \
--slug <slug> --status <status> --phase press --next <next> \
--artifact .cheese/cook/<slug>.md --orientation "<one-line orientation>" \
--durable-flags "<preserved Cook value>" --baseline "<baseline artifact path>" \
--grounded <path[#start-end]> --body-file <body-path>
status: <canonical status field>
next: age | cook | done
artifact: .cheese/cook/<slug>.md
durable_flags: <preserved Cook value>
baseline: none | <baseline artifact path>
<one-line orientation>
The handback contract defines the status: grammar. The preamble accepts no other keys. Put every Press value in the report body.
artifact: names the consumed Cook report. Do not put attack evidence on this line.
baseline: names the one artifact that Cook recorded. See ../cook/references/quality-gates.md.
Write these body sections under the preamble:
## Attempts— one row for each attempt. Give the attempt number and outcome.## Evidence— the stable attack identity, the test digest, and the failing test for a finding.## Review follow-ups— each out-of-contract concern. Writenonewhen the run records no concern. Age reads this section.
Map the outcome to the terminal preamble:
| outcome | status | next |
|---|---|---|
| GREEN | ok | age |
| GREEN with a recorded concern | ok-with-concerns: <concern> | age |
| finding (an attack test exposes a defect) | ok-with-concerns: <defect> | cook |
invalid evidence or production change (blocked) | halt: <reason> | done |
| third finding on the same attack | halt: correction-cap | done |
next: done is terminal. It never starts another phase.
A next: cook handoff is a Cook correction (correction = true). Cook fixes the defect. Press then replays the same attack.
Press enforces a correction cap. Press allows at most 2 Cook corrections for the same attack. A third finding on that attack stops with status: halt: correction-cap and next: done.
Handoff
Pipeline: culture → mold → cook → [press] → age → cure → plate
After a GREEN Press report, use the shared handoff gate. Start the review with /age <slug>.
After a finding, hand off to Cook as a correction with the failing test named in the report.
Forward --hard, --auto, and --open-pr to /age when the caller supplied them. Never add --open-pr.
Rules
- Do not edit production code, production fixtures, or production adapters.
- Do not change the attack between replays.
- Do not treat out-of-contract behavior as an implementation request. Record it under
## Review follow-ups. Report the run asok-with-concernson a GREEN pass. - Preserve baseline-aware readiness.
Discipline
Press uses evidence first. An unverified failure is not a finding.
Name the outcome before each handoff decision. Name the attack digest. Stop if one value is missing. Do not guess.
Generated bundle command inventory: references/commands.md.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/paulnsorensen/easy-cheese/press">View press on skillZs</a>