Remove unused dart_code_linter dependency and dead rules config - #213
Merged
reidbaker merged 2 commits intoAug 4, 2026
Merged
Conversation
Contributor
There was a problem hiding this comment.
Code Review
This pull request removes the dart_code_linter dependency and its configuration from pubspec.yaml and analysis_options.yaml. Feedback was provided regarding a missing trailing newline at the end of analysis_options.yaml to ensure compatibility and prevent Git warnings.
reidbaker
self-requested a review
August 4, 2026 16:06
reidbaker
approved these changes
Aug 4, 2026
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.
I should have caught this in #211 but I thought the analyzer warnings were running an action step.
Relevant prompts
Agent authored pr description
Summary
Removes
package:dart_code_linterfrompubspec.yamland deletes deaddart_code_linter:rules configuration fromanalysis_options.yaml.Motivation and Context
dart_code_linterwas declared as adev_dependencyinpubspec.yamland had 15 custom rules configured inanalysis_options.yaml. However, this package was creating a false sense of security because none of its rules were actually being executed in development or CI.Why this code was giving a false sense of security:
dart_code_linterwas intentionally omitted fromanalyzer: plugins:inanalysis_options.yaml(due to racy false positives documented in issue Flaky CI:analyze_and_test (windows-latest)intermittently fails on `dart analyze --fatal-infos #144). Consequently, standarddart analyzeignores thedart_code_linter:block entirely and only runs standard Dart SDK lints.dart_code_linterrules without an analyzer plugin, the CLI commanddart run dart_code_linter:metrics analyze lib testmust be invoked. This command was never called in.github/workflows/, pre-commit hooks, or developer verification scripts. (Note: CI'scognitive_complexitycheck usespackage:cognitive_complexity, a separate single-purpose tool).Removing this unused dependency cleans up dead configuration and removes an unmaintained dev dependency.
Related Issues
N/A
What changed
tool/dart_skills_lint/pubspec.yaml: Removeddart_code_linter: ^4.0.3fromdev_dependencies.tool/dart_skills_lint/analysis_options.yaml: Removed the deaddart_code_linter:configuration section and the accompanying comment explaining why it was omitted from analyzer plugins.Testing Instructions
dart format .to verify formatting.dart analyze --fatal-infosto verify static analysis.dart run cognitive_complexity --fail-threshold 48 tool/dart_skills_lint/lib tool/dart_skills_lint/testto verify complexity metrics.dart testto verify unit tests.dart run bin/cli.dart -d .agents/skillsto validate repository skills.