chore(skills): remove the stale test-pr-devnet skill - #564
Conversation
devnet-runner and devnet-log-review now cover everything this skill did except building a branch-specific Docker image: node roster and image tag selection, pause/unpause instability testing, and log analysis. What remained had drifted from the current local setup. It hardcoded a lean-quickstart path outside the repo, waited for exactly four `_0` containers, and grepped zeam_0/ream_0/qlean_0, so every health check and its whole result summary reported nothing against the all-ethlambda validator config the local devnet uses now.
🤖 Claude Code ReviewThis confirms the PR's claims accurately reflect Review: PR 564 — chore(skills): remove the stale test-pr-devnet skillThis is a documentation/tooling-only change (deletes an internal Findings:
No correctness, security, or performance concerns — this is a well-scoped, low-risk cleanup with a clear rationale (stale hardcoded macOS path, drifted container-name assumptions) and accurate documentation updates. Looks good to merge. Automated review by Claude (Anthropic) · sonnet · custom prompt |
🤖 Codex Code ReviewNo findings. This PR only removes the legacy Residual risk is limited to developer workflow: if the new docs pointed to missing assets, local devnet testing would regress. I checked that Automated review by OpenAI Codex · gpt-5.4 · custom prompt |
🤖 Kimi Code ReviewThis PR removes the Issues in Deleted Code (for awareness when migrating logic)File:
File:
CLAUDE.md ChangesThe documentation updates (lines 92, 99-101) correctly remove the obsolete reference and point to the replacement skills. The new references assume Summary
Automated review by Kimi (Moonshot AI) · kimi-k2.5 · custom prompt |
Greptile SummaryThis PR removes the stale
Confidence Score: 5/5The PR appears safe to merge because the deleted workflow has no remaining references and both replacement skill paths exist. The change removes only stale development tooling and updates its two documentation references to replacement skills present in the committed HEAD tree.
|
| Filename | Overview |
|---|---|
| CLAUDE.md | Removes the obsolete command and replaces its documentation link with valid references to the two replacement skills. |
| .claude/skills/test-pr-devnet/SKILL.md | Deletes stale workflow documentation whose responsibilities are intentionally delegated to maintained skills. |
| .claude/skills/test-pr-devnet/scripts/test-branch.sh | Removes the obsolete branch-image and devnet orchestration script without leaving tracked references to it. |
| .claude/skills/test-pr-devnet/scripts/check-status.sh | Removes the stale status script now superseded by devnet log-review tooling. |
| .claude/skills/test-pr-devnet/scripts/cleanup.sh | Removes cleanup logic coupled to the obsolete multi-client setup. |
Reviews (1): Last reviewed commit: "chore(skills): remove the stale test-pr-..." | Re-trigger Greptile
Removes
.claude/skills/test-pr-devnetand repoints the twoCLAUDE.mdreferences at the skills that replaced it.Why
devnet-runneranddevnet-log-reviewalready cover what this skill did:devnet-runner(node roster, timeout, automatic log dump)client-cmds/*-cmd.shimage tagsdevnet-runnerdevnet-runner/references/instability-testing.mddevnet-log-reviewscriptsWhat was left had drifted from the current local setup:
LEAN_QUICKSTART=/Users/mega/lean_consensus/lean-quickstart, whiledevnet-runnerexpectslean-quickstartat the repo root._0containers and its checks greppedzeam_0/ream_0/qlean_0, so every health check and the whole result summary reported nothing against the all-ethlambdavalidator-config.yamlthe local devnet uses now.It was last touched functionally in #414; #532 only swept it for docs consistency.
Not carried over
The one capability with no replacement is
test-branch.sh's build-tag-patch-restore step: build the current branch asghcr.io/lambdaclass/ethlambda:<branch>, pointethlambda-cmd.shat it, and restore the backup afterwards.make docker-buildonly produces:local. Left out deliberately; worth adding todevnet-runneras a small script if branch-image testing comes up again.