io.github.CloudCorpRecords/rerunplan
Rerun or fix? Classify a failed check from past-run evidence: infra flake, flaky, or real.
Que pouvez-vous faire avec io.github.CloudCorpRecords/rerunplan ?
plan_rerun— Classify a failed check from its past-run
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
@reneturcios/rerunplanclaude mcp add rerunplan -- npx -y @reneturcios/rerunplan@0.1.0 mcp
{
"mcpServers": {
"rerunplan": {
"command": "npx",
"args": [
"-y",
"@reneturcios/rerunplan@0.1.0",
"mcp"
]
}
}
}
ghcr.io/cloudcorprecords/rerunplan:0.1.0claude mcp add rerunplan -- docker run -i --rm ghcr.io/cloudcorprecords/rerunplan:0.1.0 mcp
{
"mcpServers": {
"rerunplan": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/cloudcorprecords/rerunplan:0.1.0",
"mcp"
]
}
}
}
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
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 timeflaky→ rerun — the check has passed before and has failed before with this same error signature; the failure comes and goesreal_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 failureinsufficient_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
npx @reneturcios/rerunplan plan --check unit-tests --signature "Error: boom" --past past-runs.json
npx @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
npx -y @reneturcios/rerunplan mcp
MCP client config:
{
"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 nameerror_signature(string, optional) — the current failure's error signaturepast_runs(array, required) — past runs as{check?, status, error_signature?}objects
Docker
docker run -i ghcr.io/cloudcorprecords/rerunplan
docker run --rm -v "$PWD:/w" ghcr.io/cloudcorprecords/rerunplan plan --check unit-tests --past /w/past-runs.json
Development
npm install
npm 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
Questions fréquentes
Qu'est-ce que io.github.CloudCorpRecords/rerunplan ?
Rerun or fix? Classify a failed check from past-run evidence: infra flake, flaky, or real.
Comment installer io.github.CloudCorpRecords/rerunplan ?
Il s'exécute sur votre machine. Dans Claude Code : claude mcp add rerunplan -- npx -y @reneturcios/rerunplan@0.1.0 mcp. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour io.github.CloudCorpRecords/rerunplan ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
io.github.CloudCorpRecords/rerunplan est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient io.github.CloudCorpRecords/rerunplan ?
Il est publié par CloudCorpRecords. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.