Repository navigation
docs(skill): treat shallow/file_split as advisory and add stop rule - #184
Merged
Merged
Conversation
- Add a stop rule: only declarations above the threshold are work items. - Treat shallow and file_split findings as advisory review aids; drop the batch re-inline option and --fail-on-safe-inline gate recommendations. - Add keep/revert heuristics, a hot-loop benchmark rule, and a blind self-review step for large diffs. - Reframe Pattern G in refactoring_recipes.md; name split files by contents. - Evals: replace the shallow-gate assertion, add negative assertions, and add complexity_stop_when_clean.
kevmoo
commented
Oct 9, 2026
kevmoo
left a comment
Owner
Author
There was a problem hiding this comment.
Sanity-check pass; two optional notes inline. Looks good to land otherwise.
Clarify that shallow/file_split findings are advisory in consumer repos, that a package may keep its own dogfood --fail-on-safe-inline CI step, and that existing CI gates are not removed without an explicit ask.
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.
The
dart-cognitive-complexityskill pushes agents to clear everyshallowandfile_splitfinding, which caused over-refactoring and regressions in dogfood runs.Changes
shallowandfile_splitare documented as optional review aids. Removed the "batch re-inline SAFE_INLINE" triage option and every--fail-on-safe-inlinegate recommendation. The findings-table action now reads "Review: consider re-inlining if ...".// cognitive_complexity:ignoreon the line before the declaration, plus a reason comment.refactoring_recipes.md: Pattern G no longer says "always re-inline". Pattern F now says to name split files by their contents.complexity_stop_when_clean.Docs-only: no version, pin, or CHANGELOG changes.
Evidence
Blind reviews of the dogfood PRs found that fixing CC > 15 helped, but re-inlining
SAFE_INLINEhelpers and name-by-one-function file splits mostly hurt:Related (not fixed here): #181, #183