已收錄437 則資訊/102 款 AI 工具/413 個開源專案/75 個學習資源
首頁資訊開源排行榜模型排行AI 工具Skills學習資源
首頁 / Skills / 開發提效 / 驗證即停 Verify and Stop
開發提效

驗證即停 Verify and Stop

Julius BrusseeApache-2.0Skill 語言: 英文
授權已核對不含腳本
演示真實執行紀錄 · claude-opus-5-5 · 2026年10月
Can you check whether this ticket is done? I only want to know if the acceptance criteria are met. Ticket ACME-88 acceptance criteria: 1. `GET /health` returns HTTP 200 with JSON body `{"status": "ok"}`. 2. The endpoint does not require authentication. 3. A test covers the endpoint. The developer's diff: ```python # app/routes.py @app.get("/health") @require_login def health(): return {"status": "ok"}, 200 ``` ```python # tests/test_health.py def test_health(client, logged_in_user): resp = client.get("/health") assert resp.status_code == 200 assert resp.json == {"status": "ok"} ``` CI output: `tests/test_health.py::test_health PASSED` and `142 passed in 8.31s`.
Skill: verify-and-stop

No, ACME-88 isn't done. Criterion 2 fails, and the test that's supposed to cover the endpoint wouldn't catch that failure.

# Criterion Result Evidence
1 GET /health returns 200 with {"status": "ok"} Pass, but only for logged-in users The handler returns {"status": "ok"}, 200. The test checks both the status code and the JSON body, and CI shows it passing.
2 No authentication required Fail app/routes.py puts @require_login on health(), so the endpoint requires login.
3 A test covers the endpoint Partial test_health exists and passes. But it uses the logged_in_user fixture, so it only tests a logged-in request. That's why CI passes even though criterion 2 fails.

To close the ticket:

  • Remove @require_login from health().
  • Remove logged_in_user from the test so it makes the request without logging in. That way the test also proves criterion 2.

How I checked: There's no repository in this workspace, so I didn't run anything. This is based only on the diff and CI output you pasted. I'm also assuming @require_login blocks requests that aren't logged in (with a 401, 403 or a redirect), as its name suggests. I couldn't see its code to confirm that.

Real run recorded with claude-code / claude-opus-5-5. Output is shown verbatim, unmodified.

它做什麼

一條用於純驗證任務的工作規則：把驗收條件轉成能證明它們的最少檢查，回報結果，然後停下。

運作方式

  1. 為每條驗收條件找到最少且足夠的證明，仍對應目前程式碼的既有結果直接沿用。
  2. 先執行針對性的檢查，再執行範圍較大的檢查；每項結果準確標示為通過、失敗、無法執行或被阻擋。
  3. 未被要求就不修改產品程式碼；條件符合後不再潤飾、整理或增加測試。

適合情境

「這張工單做完了嗎」的核對、合併前驗證與最後一步的確認。

需要了解

出自開源專案 Caveman 的一組通用工作方式。指令本身不帶 Caveman 品牌，放到任何專案都能使用。

說明與風險

純指令檔：沒有腳本、不連網、不寫入檔案。 壓縮檔中另附 LICENSE、NOTICE 與 agents/openai.yaml（供 Codex 使用的顯示名稱與預設提示詞）。