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 分