Repository navigation
chore(dz): fill the reviewer prompt with this repo's rules - #40
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
✅ Reviewed — nothing blocking0 actionable comment(s) · grounded on your code |
Contributor
There was a problem hiding this comment.
Review summary — 1 file(s), 0 finding(s).
Replaces reviewer setup placeholders with repository-specific compatibility, safety, testing, release, and CI rules. This documentation-only diff shows no concrete merge-blocking defect in the supplied context.
- test files were not shown to the reviewer — this diff touched no path recognised as a test, so no assertion was available to read the change against
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.
What
Replace the onboarding-floor
.dz/maintainer/reviewer.mdwith this repository's real review rules: what to reject, the gates that prove a PR, and what never to flag.Why
The reviewer prompt still carried
TODO(setup)in every section, so every review of this repo ran on no repo-specific rules.Changes
.dz/maintainer/reviewer.md: rules distilled fromAGENTS.md,.github/workflows/ci.yml,bin/check,.github/pull_request_template.md,.coderabbit.yml,apps/fast-rspec/.rubocop.ymland the gemspec (drop-in compatibility, zero runtime dependencies, native/pure parity, fork safety and determinism, real-service tests, measured claims, the public-tree guard, release-by-version-bump). Every rule cites the repo path it comes from, and every cited path exists. 7,019 characters, under the 12,000 cap.Verification
dz-contractgrade: before 1 finding (reviewer prompt still carryingTODO(setup)slots), after 0 findings (exit 0).bin/check-public-treeclean on the new tree.