docs: Explorer skip for mechanical changes + defer to repo PR template#4
Merged
Merged
Conversation
The design phase always dispatches the explorer at medium/large tier, but when the verify fact-check already contains a file-level map and the change is mechanical (pure deletion, rename, inlining), the explorer pass only duplicates it. Add a carve-out so it can be skipped in that case, recorded in _progress.md — codifying a judgment the orchestrator otherwise makes ad hoc. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01R4WLGFUppcs4tNxoNsJP2x
Step 9 hardcoded the PR body as "What we're solving / How / Alternatives and nothing else", which ignored any template a repo provides. Make that the fallback: if the repo has a PR template, mirror its headings and fill them from the run; otherwise use the plain default. Keeps shepherd repo-agnostic while honoring each repo's own PR convention. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01R4WLGFUppcs4tNxoNsJP2x
jirispilka
force-pushed
the
claude/apify-mcp-simplification-4hehpt
branch
from
July 14, 2026 09:50
9a72bb3 to
eba90f8
Compare
jirispilka
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ad-hoc — two shepherd-generality tweaks surfaced by a
/shepherd-evaluatepass on a real run. Both areSKILL.mdtext only.What changed
medium/largetier when theverifyfact-check already provides a file-level map and the change is mechanical (pure deletion, rename, inlining), recorded in_progress.md.Why
Both codify judgments the orchestrator was otherwise making ad hoc. On a mechanical run the fact-check already locates every symbol, so the explorer only reproduced it. And hardcoding the PR-body format ignored templates a repo provides — now that's the fallback, not the rule.
What I'm unsure about
Nothing outstanding — the finish-step change was merged with
main's concurrent edits to the same section (theCloses #Nclosing-keyword guidance is preserved). The contract test that pins the plain-body wording still passes.Proof it works
python -m pytest tests/→ 84 passed locally (the orchestrator-contract suite that pins these SKILL.md invariants). Rebased onto currentmain; conflict resolved.