Repository navigation
ci(prompt): add a linter coverage check to the aftermath phase - #32
Conversation
New aftermath step verifies every tracked language has a linter and that each linter runs the rules it needs, not just its default subset. Renumbers the following aftermath steps 57-63 to 58-64.
|
Warning Review limit reached
Next review available in: 52 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
WalkthroughThe CI adoption prompt expands Phase 7 from 9 to 10 aftermath steps. It adds a linter coverage audit and renumbers the review, analysis, coverage, residue, and gitlink checks. ChangesCI adoption prompt
Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
The new aftermath step left four document-wide references stating 63 steps and a 1-63 range, so an operator following the header would stop before step 64. The languages probe used 'sed s/.*\.//', which discards directory context. The linter inventory selects on paths, so that histogram cannot distinguish .github/workflows/*.yml from any other YAML and drops the 25 extensionless tracked files (.githooks/pre-commit, config, Dockerfile) that path-scoped selectors exist to cover. Replaced with an awk probe that keeps full paths and groups extensionless basenames separately.
1 participant
TL;DR
The adoption job's closing checklist tells the agent to install a lint hook, but never asks whether the linters behind that hook actually cover the repository. A tree can pass every gate while an entire language in it goes unread, or while a linter runs only its default rule subset.
Adds aftermath step 57, "Check linter coverage: languages and rules", between the commit-hook setup and the review steps, and renumbers the former steps 57–63 to 58–64.
Severity:
Low(process — closes a blind spot in the adoption checklist)What the step asks for
Three checks, each with an evidence-based not-applicable escape:
ci/linter/run-all.shand the pre-commit config.Acceptance is a file type → linter → rule profile table, with fixes landing in PR4 alongside the other aftermath work.
Renumbering
Former 57–63 become 58–64. Updated in step order along with every cross-reference: the phase table and PR table (55–63 → 55–64), the checklist line, the phase-7 preamble, the forwarding section,
steps 55–58→steps 55–59for the fix-scope note, and bothstep 62residue cross-references →step 63.Testing
Docs-only.
ci/linter/run-all.shstaged mode and the pre-commit hooks ran clean on the commit; codespell was the only lens with a file to read. No renumbered step reference remains unadjusted — verified by grepping everystep NNandNN–NNrange in the file.