referee2: split code protocol into phase-keyed sibling files#17
Open
nsmiller2501 wants to merge 2 commits into
Open
referee2: split code protocol into phase-keyed sibling files#17nsmiller2501 wants to merge 2 commits into
nsmiller2501 wants to merge 2 commits into
Conversation
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
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.
Summary
Follow-on to #11. Refactors
/referee2 codemode by splittingcode.mdinto a short orchestrator plus five phase-keyed sibling files. The deck mode is untouched.What changed
.claude/skills/referee2/code.mdshrinks from ~790 lines to a short top-of-funnel file that lists the phases and points to each sibling file. The full prose for each phase moves to its own file.code_protocol.md— the high-level Phase 0 / Phase 1 / Phase 2 ordering and what gates each transition.code_subagent_prompts.md— the exact prompts handed to each subagent (Stata, Python, R, results-comparison) so the orchestrator stays a thin coordinator.code_spec_outputs.md— the expected JSON / Markdown shapes for replication outputs.code_tainted_session.md— the "stop and report" protocol for when the host session has accumulated context that would taint the audit.code_reporting.md— the final report template and the criteria that govern severity.README.mdupdates the installation paragraph to mention the progressive-load pattern.Why
code.mdmonolith was load-once-keep-loaded: every invocation paid the full token cost even when the audit had no reason to enter (for example) the tainted-session branch.code_spec_outputs.md) is loaded only when results-comparison runs.deckmode wasn't large enough to benefit from the same treatment; it stays single-file.Testing
code.md↔ sibling-file cross-references all resolve.