Repository navigation
Count only actionable code review findings - #2129
Merged
Merged
Conversation
JacobStephens2
marked this pull request as ready for review
November 12, 2026 17:15
Merged
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
Define the same contract in the Session prompt and embedded Factory skill, regenerate the published prompts, and align the manual and hand-written process page. Findings later fixed still count. The JSON schema and retained historical metrics stay unchanged.
Closes #2051
Evidence
Execution evidence
Confirmed cause: the shared report prompt omitted an actionable-only definition, while the Factory skill allowed an unqualified finding count and explicitly included declined findings.
cargo test --bin thirdshift prompt::tests::review_reports_count_only_actionable_findingsfailed:missing "number of actionable findings".After: the same command passed (1 test).
cargo test --bin thirdshift skills::tests::code_review_reports_count_only_actionable_findingsfailed:missing "Report only actionable findings that warrant a change or human follow-up" in Factory skill.After: the same command passed (1 test).
node --test site/tests/review-counts.test.cjsfailed:docs/guide.md: stale count contract.After: the same command passed (1 test). The Spec reviewer's exact Python assertion also failed for all three published documentation paths before the fix and passed afterward.
UPDATE_PROMPTS=1 cargo test prompts_pageandcargo test prompts_page: passed (14 prompt-page tests each).npm run docs --prefix siteandnpm run docs:check --prefix site: passed.scripts/affected-tests refs/remotes/origin/main: site checks passed (50.70s); its Rust run passed the unit tests and earlier integration targets, then caught the stale exact-prompt expectation infresh_run(528.31s). Updated that expected text;cargo test --test fresh_runpassed (26 tests, 2 ignored). Continuing the 77 integration targets that the first run did not reach; completed targets use identical production sources. The continuation passed all 77 remaining targets (1039.94s, warm build cache). Together with the corrected fresh-run file, all integration targets and the unit suite are covered successfully; no equivalent full-suite repeat was needed.The first
scripts/affected-tests mainattempt selected changes from 49 commits already present on the fetched base, because localmainwas stale. Its extra Console suite failed atworking-targets.test.cjs:83(1440px remote review-explicit: visible PR target,false !== true); a directnode --test console/tests/working-targets.test.cjsrerun failed identically. No Console source or test is changed by this PR. The final affected selection uses the fetched PR base,refs/remotes/origin/main.Test seams: emitted Session prompts, the Factory skill linked into a worktree, and the published review-count documentation. These deterministic checks guard the instruction contract; they do not measure a model's compliance rate.
Visual evidence
Prompts count contract, 1440×900
Prompts count contract, 390×844
Manual count contract, 1440×900
Manual count contract, 390×844
How it works count contract, 1440×900
How it works count contract, 390×844
Review coverage
Standards: 0 findings. Spec: 1 finding, fixed in
98127183; none remain. Both reviewers read the 20 files present at98127183, including generated files. Their one follow-up was already complete when validation exposed the stale exact-prompt expectation. The latertests/fresh_run.rsexpectation update is unread by both review axes and is disclosed here; it passed its full integration-test file. No generated-output exclusions were used.Unaddressed findings
Standards
None.
Spec
None. The published-documentation finding was reproduced and fixed, with its regression retained.
Security
None.
Security review outcome
No unaddressed introduced findings.
Merge Danger
Door: two-way
Revert the instruction and documentation changes to restore the previous behavior.
Blast Radius: reviews
Future review Session prompts and documentation only; no Rust count schema change or rewrite of historical summaries.
Built with codex codex-cli 0.167.2 · gpt-6.1-sol · xhigh