Skip to content

Update tiers.json from corpus oracle#1

Merged
6 merged 1 commit intomainfrom
corpus-oracle/update-tiers-1771835730
Feb 23, 2026
Merged

Update tiers.json from corpus oracle#1
6 merged 1 commit intomainfrom
corpus-oracle/update-tiers-1771835730

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

Summary

Auto-generated from corpus oracle run. Cops with any false positives
across the corpus are demoted to preview tier.

  • Stable: cops with 0 FP across all corpus repos
  • Preview: cops with >= 1 FP

CI will validate the new tiers.json compiles and passes tests.

🤖 Generated by corpus oracle workflow

@6 6 merged commit 0b522d1 into main Feb 23, 2026
@6 6 deleted the corpus-oracle/update-tiers-1771835730 branch February 23, 2026 08:37
6 added a commit that referenced this pull request Mar 18, 2026
…patterns

Three root causes fixed:
1. collect_param_names/find_param_offset did not handle BlockParameterNode
   (&block params), making block-pass args invisible to the cop entirely.
2. AssignmentCollector did not handle MultiWriteNode (parallel/destructuring
   assignment like a, b = expr). LocalVariableTargetNode targets inside
   multi-writes were never collected as assignments.
3. The && short-circuit case was already handled by default visitor recursion;
   the actual blocker was cause #1 (&block not collected).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
6 added a commit that referenced this pull request Mar 21, 2026
Explains that ^markers are 0-indexed while diagnostic columns are
1-indexed, and shows how to use JSON output to get exact positions.
This was the #1 time sink for agents fighting fixture format.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant