Rerunplan

io.github.CloudCorpRecords由 GitHub 帳號 CloudCorpRecords 發布v0.1.0更新於 Nov 3, 2026

重跑還是修復?根據以往執行的證據對失敗的檢查進行分類:基礎設施抖動、不穩定,還是真實問題。

AI 翻譯由 AI 模型根據下方的原文描述翻譯,可能有誤。

原文描述

Rerun or fix? Classify a failed check from past-run evidence: infra flake, flaky, or real.

已驗證STDIO僅桌面

概覽

Rerunplan 的本機 MCP 服務;無需登入;STDIO。

暫無 AI 概覽:以下資訊來自註冊中心條目和服務本身。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Rerunplan,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

rerunplan

A check failed. Rerun it, or fix it? rerunplan classifies the failure from evidence — the failing check's name, its error signature, and past runs of the same check — and answers with a classification, a recommendation, and the evidence lines that drove the call:

  • infra_flake → rerun — the error signature matches a known infrastructure pattern (timeout, connection reset, DNS, rate limit, runner loss, gateway errors) and the check is not failing that way every time
  • flaky → rerun — the check has passed before and has failed before with this same error signature; the failure comes and goes
  • real_failure → fix — the check fails in every usable past run (with the current signature, when one is given); an infra-looking signature that fails every time is still a real failure
  • insufficient_evidence → investigate — no usable history, or a mixed history no rule claims

Rules fire in a fixed order and each appends its evidence. Statuses are normalised (success/pass/passed, failure/fail/failed/error); runs for other checks are ignored. Pure local computation: no network, no configuration.

CLI

bash
npx @reneturcios/rerunplan plan --check unit-tests --signature "Error: boom" --past past-runs.jsonnpx @reneturcios/rerunplan --version

past-runs.json is a JSON array of {"check": "unit-tests", "status": "failure", "error_signature": "Error: boom"} objects (check and error_signature optional per run).

Exit codes: 0 on success, 1 on a runtime error (including an unreadable or invalid past-runs file), 2 on a usage error.

MCP server

bash
npx -y @reneturcios/rerunplan mcp

MCP client config:

json
{  "mcpServers": {    "rerunplan": {      "command": "npx",      "args": ["-y", "@reneturcios/rerunplan", "mcp"]    }  }}

Tools

  • plan_rerun — Classify a failed check from its past-run history and recommend rerun, fix, or investigate.
    • check (string, required) — the failed check's name
    • error_signature (string, optional) — the current failure's error signature
    • past_runs (array, required) — past runs as {check?, status, error_signature?} objects

Docker

bash
docker run -i ghcr.io/cloudcorprecords/rerunplandocker run --rm -v "$PWD:/w" ghcr.io/cloudcorprecords/rerunplan plan --check unit-tests --past /w/past-runs.json

Development

bash
npm installnpm run build   # tsc -> dist/npm test        # tsx --test test/*.test.ts (pure local, no network)npm run dev     # run the CLI from source

License

MIT — Copyright (c) 2026 Rene Turcios

來源:README.md,提交 c90106a

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.1.0最新Nov 3, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分