🎯 零依赖、纯标准库、离线的确定性验收断言与规格追溯 CLI | Deterministic acceptance verdicts & spec traceability for AI-assisted development
Repo gitstq/ClaimCheck, read from GitHub 1 min ago. gitstq has not joined Take My Repo.
gitstq/ClaimCheck is a public repo on GitHub by gitstq. 🎯 零依赖、纯标准库、离线的确定性验收断言与规格追溯 CLI | Deterministic acceptance verdicts & spec traceability for AI-assisted development. It declares the MIT license on GitHub. It is written mainly in Python, has 0 stars and last changed on 2026-11-08. Nobody has reviewed it on Take My Repo yet, which says nothing about its quality. Read from GitHub on 2026-11-21.
In the maintainer's words. Shown from GitHub; Take My Repo does not keep a copy.
让 AI 的每一句「已完成」,都有可复现、可审计的确定性裁决。 Every "it's done" from an AI deserves a reproducible, deterministic verdict.
🌐 选择语言 / 選擇語言 / Choose your language 简体中文 · 繁體中文 · English
📌 本项目属于 CLI 工具 / 脚本库 类型,按发布规范无需 Release 附件; 安装、集成与 CI 用法在下文三语版本中均有完整说明。
ClaimCheck 是一个零依赖、纯标准库、100% 离线的验收断言与规格追溯 CLI。它解决的痛点非常具体:AI 编码助手会自信地说「功能已完成、测试已通过、文档已补齐」,但这类声明本质上是不可验证的自然语言。ClaimCheck 把验收条件写成一份声明式 claims.json,再用确定性检查器逐条裁决,输出人可读报告、机读 JSON 与 CI 退出码。
同时它提供独家的 规格 → 实现追溯矩阵:在代码注释里写上 @claim:C-001,工具即可扫描全仓库,告诉你哪些验收断言真的有代码承接、哪些是空头支票、哪些标记引用了不存在的断言。
💡 灵感来源:参考了 GitHub Trending 上
github/spec-kit(规范驱动开发)与2akouwu/reverify(「AI 提议,确定性工具裁决」)的产品逻辑与痛点,代码 100% 独立自研,未复制任何一行原项目实现。✨ 自研差异化亮点:相比依赖 AI Agent / uv 的模板式工具,ClaimCheck 完全离线、结果可复现、原生支持 CI,并额外提供 spec-kit 所没有的追溯矩阵、孤儿标记检测与安全执行闸门。
| 特性 | 说明 |
|---|---|
| 🎯 确定性裁决 | 12 种内置检查器,同样的输入永远得到同样的结论,不调用模型、不联网、无随机性 |
| 🔗 规格追溯矩阵 | 扫描 @claim:<ID> 标记,输出覆盖率、逐条实现文件与 孤儿标记 告警 |
| 📄 三种输出格式 | text / json / markdown,所有子命令统一支持 |
| 🧱 CI 原生 | 退出码 0 通过 / 1 失败 / 2 配置错误,--strict 可把覆盖率纳入门禁 |
| 🚀 一键生成示例 | claimcheck init 生成一个自检即全绿的迷你项目,30 秒上手 |
| 📦 零依赖打包 | build.py 仅用标准库产出合规 wheel + sdist,Windows / macOS / Linux 行为一致 |
| 🔒 安全闸门 | command_exit 默认关闭,需显式 --allow-commands;所有路径被限制在项目根目录内 |
| 🌐 三语文档 | 简体中文 / 繁體中文 / English 完整镜像,非机翻 |
| 🤝 自举校验 | examples/claims.json 让 ClaimCheck 校验 ClaimCheck 自己,并跑在 CI 里 |
环境要求:Python 3.8+,无需任何第三方包、无需网络、无需 API Key。
# 方式一:从源码直接运行(零安装) git clone https://github.com/gitstq/ClaimCheck.git cd ClaimCheck python -m claimcheck --version # 方式二:安装为命令行工具 python -m pip install -e . claimcheck --version # 方式三:安装构建产物 python build.py python -m pip install --no-index --find-links dist claimcheck
30 秒体验 🎬
claimcheck init --dir ./my-demo --force # 生成自洽的示例项目 claimcheck check --root ./my-demo # 全部断言通过 → VERDICT: PASS claimcheck trace --root ./my-demo --format markdown claimcheck checkers # 查看 12 个内置检查器
📷 演示截图占位:
docs/screenshots/verdict-text.png(终端裁决输出)、docs/screenshots/trace-matrix.png(Markdown 追溯矩阵)。可在 Issue 中提交你的截图。
{
"version": "1",
"project": "my-service",
"claims": [
{
"id": "C-001",
"title": "README 必须存在",
"spec": "SPEC-01",
"type": "file_exists",
"path": "README.md"
},
{
"id": "C-002",
"title": "离线模式必须开启",
"spec": "SPEC-02",
"type": "json_path",
"path": "config.json",
"json_path": "runtime.offline",
"equals": true
},
{
"id": "C-003",
"title": "源码不得残留 TODO",
"spec": "SPEC-03",
"type": "file_not_contains",
"path": "src/main.py",
"pattern": "\\bTODO\\b"
}
]
}必填字段只有 id、title、type;其余字段随检查器而定。enabled: false 可临时停用某条断言。
| 类型 | 作用 | 关键参数 |
|---|---|---|
file_exists |
文件存在 | path |
dir_exists |
目录存在 | path |
file_not_exists |
文件必须不存在 | path |
glob_count |
glob 命中数量在 [min, max] |
pattern, min, max |
file_contains |
正则/字面量出现次数达标 | pattern 或 literal, flags, min, max |
file_not_contains |
禁止出现某内容 | 同上 |
file_matches |
全文匹配(search/match/fullmatch) |
pattern, mode, expect |
text_count |
行数/字符数/字节数/出现次数约束 | kind, min, max |
json_path |
JSON 路径存在或取值相等 | json_path, equals, exists |
json_schema_lite |
轻量 schema(必填/类型/等值/禁用) | required, types, equals, forbidden |
hash_equals |
文件哈希一致 | algo, expected |
command_exit |
命令退出码(默认禁用) | command, expect_code, timeout |
🔎
flags支持IGNORECASE、MULTILINE、DOTALL、VERBOSE、ASCII;json_path支持点号与索引,例如services[0].enabled。
claimcheck check -c claims.json --root . # 文本裁决 claimcheck check --format json -o report.json # 机读报告 claimcheck check --format markdown -o report.md # Markdown 报告 claimcheck check --allow-commands # 打开命令检查闸门 claimcheck trace -c claims.json --format markdown # 追溯矩阵 claimcheck trace --include "src/**/*.py" --strict # 限定范围 + 覆盖门禁 claimcheck report -i report.json --format markdown # 重新渲染已存报告 claimcheck checkers --format json # 列出检查器 claimcheck init --dir ./demo --force # 生成示例
| 参数 | 默认值 | 说明 |
|---|---|---|
-c, --claims |
claims.json |
声明文件路径 |
--root |
. |
被检查的项目根目录 |
--format |
text |
text / json / markdown |
-o, --output |
stdout | 输出到文件 |
--allow-commands |
关闭 | 仅在可信隔离环境开启 |
--command-timeout |
20 |
命令超时(秒) |
--strict |
关闭 | 追溯未覆盖即返回 1 |
--quiet |
关闭 | 仅输出结论行 |
见 .env.example:CLAIMCHECK_CLAIMS、CLAIMCHECK_ROOT、CLAIMCHECK_FORMAT、CLAIMCHECK_ALLOW_COMMANDS、CLAIMCHECK_COMMAND_TIMEOUT。不设置任何变量也能正常运行。
claims.json,CI 里 claimcheck check 决定能否合并。claimcheck trace --strict 阻止「规格写了但没人实现」。examples/claims.json 检查 README、LICENSE、版本号、测试文件是否齐全。| 问题 | 解决方式 |
|---|---|
报 path escapes the project root |
路径越界被安全拦截,改用 --root 下的相对路径 |
结果出现 ERR! 而非 FAIL |
断言配置有误(缺参数/非法正则/非法 JSON),按提示修正 claims.json |
command_exit 一直是 SKIP |
设计如此,需显式 --allow-commands |
| 中文内容匹配不到 | 加 "flags": ["IGNORECASE"] 或检查文件编码(工具按 UTF-8 读取) |
设计理念:把「验收」从主观判断降维成可重复执行的纯函数。每个检查器都是 (claim, context) → outcome 的纯函数,不依赖时间、网络、模型或全局状态,因此结论可以在任何机器上复现。
技术选型:只用 Python 标准库(argparse、json、re、hashlib、pathlib、subprocess、dataclasses)。理由是验收工具本身必须极易安装、极易审计、绝不引入供应链风险;构建脚本同样只用标准库,避免 build 后端带来的网络依赖。
迭代规划 🗺️:
v1.1 增加 yaml_path、env_equals、http_status(可选离线 mock)检查器v1.2 输出 SARIF,直接对接 GitHub Code Scanningv1.3 断言分组、依赖顺序与 --only/--skip 过滤v2.0 插件机制,允许外部注册自定义检查器本项目是 CLI 工具 / 脚本库,按发布规范不需要上传 Release 二进制附件。
python -m unittest discover -s tests -v # 1️⃣ 全量自测 python build.py # 2️⃣ 测试 + 构建 wheel/sdist + 完整性校验 ls dist/ # 3️⃣ 产物:.whl、.tar.gz、SHA256SUMS.txt python -m pip install --no-index --find-links dist claimcheck claimcheck --version # 4️⃣ 验证入口点
跨平台 ✅:build.py 是纯 Python,在 Windows / macOS / Linux 上生成同样的产物;Windows 用户也可运行 powershell -File scripts/verify.ps1 一键验证。
CI 集成示例 📋:
- run: python -m claimcheck check -c claims.json --root . --format markdown - run: python -m claimcheck trace -c claims.json --root . --strict
兼容环境:Python 3.8 ~ 3.12,任何支持 UTF-8 终端的操作系统;无第三方依赖、无编译步骤、无网络要求。
欢迎提交 Issue 与 PR!请先阅读 CONTRIBUTING.md。
claimcheck --version、Python 版本、脱敏后的 claims.json、期望与实际结论feat: / fix: / docs: / refactor: / test:)本项目采用 MIT License,可自由使用、复制、修改、商用,仅需保留版权声明。贡献即视为同意以 MIT 协议授权。
ClaimCheck 是一套零依賴、純標準庫、100% 離線的驗收斷言與規格追溯 CLI。它要解決的痛點很明確:AI 編碼助手總能自信地說「功能已完成、測試已通過、文件已補齊」,但這類陳述本質上是無法驗證的自然語言。ClaimCheck 把驗收條件寫成宣告式 claims.json,再以確定性檢查器逐條裁決,輸出人類可讀報告、機器可讀 JSON 與 CI 結束碼。
它還提供獨特的規格 → 實作追溯矩陣:在程式註解寫下 @claim:C-001,工具便能掃描整個專案,告訴你哪些驗收斷言真的有程式承接、哪些是空頭支票、哪些標記參照了不存在的斷言。
💡 靈感來源:參考 GitHub Trending 上
github/spec-kit(規格驅動開發)與2akouwu/reverify(「AI 提議,確定性工具裁決」)的產品邏輯與痛點;程式碼 100% 獨立自研,未複製任何一行原專案實作。✨ 自研差異化亮點:相較於依賴 AI Agent / uv 的範本型工具,ClaimCheck 完全離線、結果可重現、原生支援 CI,並額外提供 spec-kit 沒有的追溯矩陣、孤兒標記偵測與安全執行閘門。
| 特性 | 說明 |
|---|---|
| 🎯 確定性裁決 | 12 種內建檢查器,相同輸入永遠得到相同結論,不呼叫模型、不連網、無隨機性 |
| 🔗 規格追溯矩陣 | 掃描 @claim:<ID> 標記,輸出覆蓋率、逐條實作檔案與孤兒標記警示 |
| 📄 三種輸出格式 | text / json / markdown,所有子命令一致支援 |
| 🧱 CI 原生 | 結束碼 0 通過 / 1 失敗 / 2 設定錯誤,--strict 可把覆蓋率納入門檻 |
| 🚀 一鍵產生範例 | claimcheck init 產生自檢即全綠的迷你專案,30 秒上手 |
| 📦 零依賴打包 | build.py 僅用標準庫產出合規 wheel + sdist,Windows / macOS / Linux 行為一致 |
| 🔒 安全閘門 | command_exit 預設關閉,需顯式 --allow-commands;所有路徑限制於專案根目錄 |
| 🌐 三語文件 | 簡體中文 / 繁體中文 / English 完整對映,非機器翻譯 |
| 🤝 自舉校驗 | examples/claims.json 讓 ClaimCheck 檢查 ClaimCheck 自己,並在 CI 中執行 |
環境需求:Python 3.8+,不需任何第三方套件、不需網路、不需 API Key。
# 方式一:直接從原始碼執行(免安裝) git clone https://github.com/gitstq/ClaimCheck.git cd ClaimCheck python -m claimcheck --version # 方式二:安裝成指令工具 python -m pip install -e . claimcheck --version # 方式三:安裝建置產物 python build.py python -m pip install --no-index --find-links dist claimcheck
30 秒體驗 🎬
claimcheck init --dir ./my-demo --force # 產生自洽範例專案 claimcheck check --root ./my-demo # 全部通過 → VERDICT: PASS claimcheck trace --root ./my-demo --format markdown claimcheck checkers # 查看 12 個內建檢查器
📷 示範截圖占位:
docs/screenshots/verdict-text.png(終端裁決輸出)、docs/screenshots/trace-matrix.png(Markdown 追溯矩陣),歡迎於 Issue 提交你的截圖。
{
"version": "1",
"project": "my-service",
"claims": [
{
"id": "C-001",
"title": "README 必須存在",
"spec": "SPEC-01",
"type": "file_exists",
"path": "README.md"
},
{
"id": "C-002",
"title": "離線模式必須開啟",
"spec": "SPEC-02",
"type": "json_path",
"path": "config.json",
"json_path": "runtime.offline",
"equals": true
},
{
"id": "C-003",
"title": "原始碼不得殘留 TODO",
"spec": "SPEC-03",
"type": "file_not_contains",
"path": "src/main.py",
"pattern": "\\bTODO\\b"
}
]
}必填欄位僅 id、title、type;其餘依檢查器而定。enabled: false 可暫時停用單條斷言。
| 類型 | 作用 | 關鍵參數 |
|---|---|---|
file_exists |
檔案存在 | path |
dir_exists |
目錄存在 | path |
file_not_exists |
檔案必須不存在 | path |
glob_count |
glob 命中數量落於 [min, max] |
pattern, min, max |
file_contains |
正則/字面量出現次數達標 | pattern 或 literal, flags, min, max |
file_not_contains |
禁止出現某內容 | 同上 |
file_matches |
全文比對(search/match/fullmatch) |
pattern, mode, expect |
text_count |
行數/字元數/位元組數/出現次數約束 | kind, min, max |
json_path |
JSON 路徑存在或取值相等 | json_path, equals, exists |
json_schema_lite |
輕量 schema(必填/型別/等值/禁用) | required, types, equals, forbidden |
hash_equals |
檔案雜湊一致 | algo, expected |
command_exit |
命令結束碼(預設禁用) | command, expect_code, timeout |
🔎
flags支援IGNORECASE、MULTILINE、DOTALL、VERBOSE、ASCII;json_path支援點號與索引,例如services[0].enabled。
claimcheck check -c claims.json --root . # 文字裁決 claimcheck check --format json -o report.json # 機器可讀報告 claimcheck check --format markdown -o report.md # Markdown 報告 claimcheck check --allow-commands # 開啟命令檢查閘門 claimcheck trace -c claims.json --format markdown # 追溯矩陣 claimcheck trace --include "src/**/*.py" --strict # 限定範圍 + 覆蓋門檻 claimcheck report -i report.json --format markdown # 重新渲染已存報告 claimcheck checkers --format json # 列出檢查器 claimcheck init --dir ./demo --force # 產生範例
| 參數 | 預設值 | 說明 |
|---|---|---|
-c, --claims |
claims.json |
宣告檔路徑 |
--root |
. |
被檢查的專案根目錄 |
--format |
text |
text / json / markdown |
-o, --output |
stdout | 輸出至檔案 |
--allow-commands |
關閉 | 僅在可信隔離環境開啟 |
--command-timeout |
20 |
命令逾時(秒) |
--strict |
關閉 | 追溯未覆蓋即回傳 1 |
--quiet |
關閉 | 僅輸出結論行 |
參見 .env.example:CLAIMCHECK_CLAIMS、CLAIMCHECK_ROOT、CLAIMCHECK_FORMAT、CLAIMCHECK_ALLOW_COMMANDS、CLAIMCHECK_COMMAND_TIMEOUT。完全不設定也能正常運作。
claims.json,CI 以 claimcheck check 決定能否合併claimcheck trace --strict 阻止「規格寫了卻沒人實作」examples/claims.json 檢查 README、LICENSE、版本號、測試檔是否齊全| 問題 | 解決方式 |
|---|---|
出現 path escapes the project root |
路徑越界遭安全攔截,改用 --root 下的相對路徑 |
結果是 ERR! 而非 FAIL |
斷言設定有誤(缺參數/非法正則/非法 JSON),依提示修正 claims.json |
command_exit 始終為 SKIP |
設計如此,需顯式 --allow-commands |
| 中文內容比對不到 | 加上 "flags": ["IGNORECASE"],或確認檔案編碼(工具以 UTF-8 讀取) |
設計理念:把「驗收」從主觀判斷降維成可重複執行的純函式。每個檢查器都是 (claim, context) → outcome 的純函式,不依賴時間、網路、模型或全域狀態,因此結論能在任何機器上重現。
技術選型:只使用 Python 標準庫(argparse、json、re、hashlib、pathlib、subprocess、dataclasses)。原因是驗收工具本身必須極易安裝、極易稽核、絕不引入供應鏈風險;建置腳本同樣只用標準庫,避開 build 後端帶來的網路依賴。
迭代規劃 🗺️:
v1.1 新增 yaml_path、env_equals、http_status(可選離線 mock)檢查器v1.2 輸出 SARIF,直接對接 GitHub Code Scanningv1.3 斷言分組、依賴順序與 --only/--skip 過濾v2.0 外掛機制,允許外部註冊自訂檢查器本專案屬 CLI 工具 / 指令稿庫,依發布規範不需要上傳 Release 二進位附件。
python -m unittest discover -s tests -v # 1️⃣ 全量自測 python build.py # 2️⃣ 測試 + 建置 wheel/sdist + 完整性校驗 ls dist/ # 3️⃣ 產物:.whl、.tar.gz、SHA256SUMS.txt python -m pip install --no-index --find-links dist claimcheck claimcheck --version # 4️⃣ 驗證進入點
跨平台 ✅:build.py 為純 Python,在 Windows / macOS / Linux 產生相同產物;Windows 使用者亦可執行 powershell -File scripts/verify.ps1 一鍵驗證。
CI 整合範例 📋:
- run: python -m claimcheck check -c claims.json --root . --format markdown - run: python -m claimcheck trace -c claims.json --root . --strict
相容環境:Python 3.8 ~ 3.12,任何支援 UTF-8 終端機的作業系統;無第三方依賴、無編譯步驟、無網路需求。
歡迎提交 Issue 與 PR,請先閱讀 CONTRIBUTING.md。
claimcheck --version、Python 版本、去識別化後的 claims.json、期望與實際結論feat: / fix: / docs: / refactor: / test:)本專案採用 MIT License,可自由使用、複製、修改、商用,僅需保留版權聲明。貢獻即視為同意以 MIT 協議授權。
ClaimCheck is a zero-dependency, standard-library-only, fully offline CLI for acceptance verdicts and spec traceability. It tackles one sharp problem: AI coding assistants confidently claim "the feature is done, tests pass, docs are complete" — but those are unverifiable natural-language statements. ClaimCheck turns acceptance criteria into a declarative claims.json, adjudicates every item with deterministic checkers, and emits a human-readable report, machine-readable JSON, and a CI-native exit code.
It also ships a spec-to-implementation traceability matrix: drop @claim:C-001 into a code comment and ClaimCheck scans the whole tree to reveal which assertions are actually backed by code, which are empty promises, and which markers reference assertions that do not exist.
💡 Inspiration: we studied the product logic and pain points of
github/spec-kit(spec-driven development) and2akouwu/reverify("it proposes, deterministic tools decide") on GitHub Trending. The implementation is 100% original — not a single line was copied from either project.✨ What we do differently: unlike template kits that require an AI agent or
uv, ClaimCheck is fully offline, reproducible, and CI-native, and adds capabilities spec-kit does not have: a traceability matrix, orphan-marker detection, and a safety gate on command execution.
| Feature | Details |
|---|---|
| 🎯 Deterministic verdicts | 12 built-in checkers; identical inputs always yield identical outcomes — no model calls, no network, no randomness |
| 🔗 Traceability matrix | Scans @claim:<ID> markers for coverage, implementing files, and orphan markers |
| 📄 Three output formats | text / json / markdown, consistent across every subcommand |
| 🧱 CI-native | Exit codes 0 passed / 1 failed / 2 config error; --strict gates on coverage |
| 🚀 Instant demo | claimcheck init generates a self-consistent project that passes check immediately |
| 📦 Zero-dependency build | build.py produces a valid wheel + sdist using only the standard library, identically on all platforms |
| 🔒 Safety gate | command_exit is off by default and requires --allow-commands; every path is confined to the project root |
| 🌐 Trilingual docs | 简体中文 / 繁體中文 / English, fully mirrored and natively written |
| 🤝 Self-hosting | examples/claims.json makes ClaimCheck verify ClaimCheck itself in CI |
Requirements: Python 3.8+. No third-party packages, no network, no API key.
# Option 1: run straight from source (no install) git clone https://github.com/gitstq/ClaimCheck.git cd ClaimCheck python -m claimcheck --version # Option 2: install as a CLI python -m pip install -e . claimcheck --version # Option 3: install the built artifacts python build.py python -m pip install --no-index --find-links dist claimcheck
Try it in 30 seconds 🎬
claimcheck init --dir ./my-demo --force # generate a self-consistent demo claimcheck check --root ./my-demo # everything passes → VERDICT: PASS claimcheck trace --root ./my-demo --format markdown claimcheck checkers # list all 12 built-in checkers
📷 Screenshot placeholders:
docs/screenshots/verdict-text.png(terminal verdict),docs/screenshots/trace-matrix.png(Markdown matrix). Contributions welcome!
{
"version": "1",
"project": "my-service",
"claims": [
{
"id": "C-001",
"title": "README must exist",
"spec": "SPEC-01",
"type": "file_exists",
"path": "README.md"
},
{
"id": "C-002",
"title": "Offline mode must be enabled",
"spec": "SPEC-02",
"type": "json_path",
"path": "config.json",
"json_path": "runtime.offline",
"equals": true
},
{
"id": "C-003",
"title": "No leftover TODO in source",
"spec": "SPEC-03",
"type": "file_not_contains",
"path": "src/main.py",
"pattern": "\\bTODO\\b"
}
]
}Only id, title and type are required; all other keys depend on the checker. Set enabled: false to temporarily disable a claim.
| Type | Purpose | Key options |
|---|---|---|
file_exists |
A file exists | path |
dir_exists |
A directory exists | path |
file_not_exists |
A file must be absent | path |
glob_count |
Glob matches fall within [min, max] |
pattern, min, max |
file_contains |
Regex/literal occurrence count | pattern or literal, flags, min, max |
file_not_contains |
Forbid a pattern | same as above |
file_matches |
Whole-text match (search/match/fullmatch) |
pattern, mode, expect |
text_count |
Lines / chars / bytes / occurrences | kind, min, max |
json_path |
JSON path exists or equals a value | json_path, equals, exists |
json_schema_lite |
Lightweight schema (required/types/equals/forbidden) | required, types, equals, forbidden |
hash_equals |
File digest matches | algo, expected |
command_exit |
Command exit code (disabled by default) | command, expect_code, timeout |
🔎
flagsacceptsIGNORECASE,MULTILINE,DOTALL,VERBOSE,ASCII;json_pathsupports dots and indices, e.g.services[0].enabled.
claimcheck check -c claims.json --root . # text verdict claimcheck check --format json -o report.json # machine-readable claimcheck check --format markdown -o report.md # Markdown report claimcheck check --allow-commands # open the command gate claimcheck trace -c claims.json --format markdown # traceability matrix claimcheck trace --include "src/**/*.py" --strict # scoped scan + coverage gate claimcheck report -i report.json --format markdown # re-render a saved report claimcheck checkers --format json # list checkers claimcheck init --dir ./demo --force # generate a demo
| Option | Default | Meaning |
|---|---|---|
-c, --claims |
claims.json |
Path to the claims document |
--root |
. |
Project root to inspect |
--format |
text |
text / json / markdown |
-o, --output |
stdout | Write to a file |
--allow-commands |
off | Only enable in a trusted, isolated runner |
--command-timeout |
20 |
Command timeout in seconds |
--strict |
off | Return 1 when coverage is incomplete |
--quiet |
off | Print only the verdict line |
See .env.example: CLAIMCHECK_CLAIMS, CLAIMCHECK_ROOT, CLAIMCHECK_FORMAT, CLAIMCHECK_ALLOW_COMMANDS, CLAIMCHECK_COMMAND_TIMEOUT. None of them are required — ClaimCheck works with a clean environment.
claims.json, then let claimcheck check decide whether the PR may merge.claimcheck trace --strict blocks "specified but never implemented".examples/claims.json verifies that README, LICENSE, version and tests are all present.| Symptom | Fix |
|---|---|
path escapes the project root |
The safety guard rejected a traversal; use a relative path under --root |
ERR! instead of FAIL |
The claim is misconfigured (missing option / bad regex / invalid JSON); follow the message |
command_exit stays SKIP |
By design — pass --allow-commands explicitly |
| CJK text does not match | Add "flags": ["IGNORECASE"] or check encoding (files are read as UTF-8) |
Design principle: reduce acceptance from a subjective judgement to a repeatable pure function. Every checker is (claim, context) → outcome with no dependency on time, network, models or global state, so a verdict reproduces on any machine.
Tech choices: standard library only (argparse, json, re, hashlib, pathlib, subprocess, dataclasses). An acceptance tool must be trivial to install, trivial to audit, and free of supply-chain risk; the build script follows the same rule to avoid a network-dependent build backend.
Roadmap 🗺️:
v1.1 — yaml_path, env_equals, optional offline http_status checkersv1.2 — SARIF output for GitHub Code Scanningv1.3 — claim groups, dependency ordering, --only/--skip filtersv2.0 — plugin API for externally registered checkersClaimCheck is a CLI tool / library. Per the release policy, it does not require binary Release assets.
python -m unittest discover -s tests -v # 1️⃣ full self-test python build.py # 2️⃣ tests + wheel/sdist + integrity checks ls dist/ # 3️⃣ .whl, .tar.gz, SHA256SUMS.txt python -m pip install --no-index --find-links dist claimcheck claimcheck --version # 4️⃣ verify the entry point
Cross-platform ✅: build.py is pure Python and yields identical artifacts on Windows / macOS / Linux. Windows users can also run powershell -File scripts/verify.ps1 for a one-command verification.
CI snippet 📋:
- run: python -m claimcheck check -c claims.json --root . --format markdown - run: python -m claimcheck trace -c claims.json --root . --strict
Compatible environments: Python 3.8 – 3.12, any OS with a UTF-8 terminal; no third-party dependencies, no compilation, no network access.
Issues and PRs are welcome — please read CONTRIBUTING.md first.
claimcheck --version, your Python version, a redacted claims.json, and expected vs. actual verdict.feat: / fix: / docs: / refactor: / test:).Released under the MIT License — use, copy, modify and commercialize freely, with the copyright notice retained. Contributing implies agreement to MIT licensing.
⭐ 如果 ClaimCheck 帮到你,欢迎点个 Star · ⭐ Star us if this helps your workflow
gitstq/ClaimCheck is a public repo on GitHub by gitstq. 🎯 零依赖、纯标准库、离线的确定性验收断言与规格追溯 CLI | Deterministic acceptance verdicts & spec traceability for AI-assisted development.
It declares the MIT license on GitHub.
Its maker has not tagged a system, so it is unknown here. Its README says what it needs.
Open "Take it" on its page: Take My Repo writes an install plan for your machine and hands it to your AI agent (Claude Code, Codex or Cursor), which asks you before each step. Take My Repo has not tested it on any machine.
Its last change on GitHub was on 2026-11-08. Take My Repo does not judge from that whether it is maintained.
Nobody has reviewed it on Take My Repo yet, which says nothing about its quality.
Run your GitHub Actions locally 🚀
Reverse engineer anything with agents, from app behavior down to native binaries.

The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.

ADB 驱动的 Android 虚拟定位 CLI:常驻推送、坐标系统一换算、GPX 轨迹回放。零 npm 依赖,无需 root。
Cheapest AI API Gateway | GPT-4o/Claude/Gemini at 0.09x cost | 1:1 CNY:USD recharge | 100% official pool | OpenAI compatible | ahg.codes
🔬 HexScope — 零依赖·离线优先的二进制文件取证探查工具箱 | Zero-dependency binary forensics workbench: hex dump, magic detection, entropy, strings, histogram, binary diff & file carving
BlueEagle AI Gateway | 蓝鹰AI网关 - Cheapest AI API Gateway | 0.09x cost | 1:1 recharge | GPT-4o Claude Gemini DeepSeek | OpenAI compatible | 最便宜AI中转站
🔌 Zero-dependency, offline-first Protocol Buffers wire toolkit: schema-less forensics, typed codec, lossless JSON bridge and 13-rule schema compatibility CI gate
BlueEagle AI Gateway - 0.09x rate, 1:1 CNY/USD | Unified API for GPT/Claude/Gemini | 100% native official pool | OpenAI compatible
This page is also available as structured data, with the same sources and dates.
/api/v1/resources/gh/gitstq/ClaimCheckTake My Repo has not tested this on your machine. Requirements come from the project's own documentation.