测试与安全

hard-cheese

paulnsorensen/e…y-cheese

Checks whether an author can explain a code change before review. Use when the user requests `/hard-cheese`, `/cheese --hard`, or an understanding check. Use it before a pull request or through the `--hard` pipeline flag. Do not use it for reviews, test hardening, or fixes.

  • 660 次安装
  • 19 星标
  • 收录于

安装命令

npx skills add https://github.com/paulnsorensen/easy-cheese --skill hard-cheese

SKILL.md

/hard-cheese

The gate reduces epistemic debt. This debt exists when code passes checks, but the author cannot explain it.

Inputs

/hard-cheese [<slug>] [--socratic-cap N=3] [--passing-score N=3] [--no-judge]

Arguments:

  • <slug> identifies the artifact at .cheese/hard-cheese/<slug>.md. This argument is optional. Without it, use the short SHA of HEAD. An explicit slug overrides the SHA.
  • --socratic-cap N sets the maximum number of retries. The gate then marks the artifact FAILED and returns a non-zero status. The default is 3. Vibecheck has no limit, but easy-cheese prevents infinite loops.
  • --passing-score N sets the minimum SOLO score for PASS. Use a value from 1 through 5. The default is 3. The gate treats a previous PASS below this value as stale.
  • --no-judge enables log-only mode. Record the user's explanation with status: LOGGED. Do not start the judge sub-agent. This mode is the easy-cheese equivalent of the optional JSONL telemetry mode in vibecheck. It retains more content. See ## Divergence from the paper.

Invocation modes