Skip to content

docs: lintScopes has shipped — present tense, and what a warning means - #96

Merged
khaliqgant merged 1 commit into
mainfrom
docs/lintscopes-shipped
Aug 15, 2026
Merged

docs: lintScopes has shipped — present tense, and what a warning means#96
khaliqgant merged 1 commit into
mainfrom
docs/lintscopes-shipped

Conversation

@khaliqgant

@khaliqgant khaliqgant commented Aug 15, 2026

Copy link
Copy Markdown
Member

lintScopes() is live in persona-kit 4.1.42 (AgentWorkforce/workforce#311, published today), so the hedge that it wasn't released yet is now wrong in the other direction — it would leave authors checking by eye while the tool is already doing it.

Also adds the inference that makes the warning actionable rather than noise: a correctly picker-gated collection is not flagged, so a warning on one means the narrowing isn't actually wired up. All four conditions have to line up (optional, enabledByInput, the bare collection path, a matching picker) and missing any one silently falls back to mirroring everything.

Verified against the real fleet: all eight watchdog personas lint clean on Slack except the one that is deliberately broad and documented.

Review in cubic

`lintScopes()` is live in persona-kit 4.1.42 (workforce#311, published today),
so the hedge that it was not released yet is now wrong in the other direction:
it would leave authors checking by eye while the tool is already doing it.

Also adds the inference that makes the warning actionable rather than noise. A
correctly picker-gated collection is NOT flagged, so a warning on one means the
narrowing is not actually wired up. All four conditions have to line up —
`optional`, `enabledByInput`, the bare collection path, and a matching `picker`
— and missing any one silently falls back to mirroring everything.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@cursor

cursor Bot commented Aug 15, 2026

Copy link
Copy Markdown

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@coderabbitai

coderabbitai Bot commented Aug 15, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@khaliqgant, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 4 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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 5d77f7f3-935a-4ed5-90d2-6f1f4b3b295f

📥 Commits

Reviewing files that changed from the base of the PR and between 86320b0 and 8bcc5ec.

📒 Files selected for processing (1)
  • skills/creating-cloud-persona/SKILL.md

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

Re-trigger cubic

@khaliqgant
khaliqgant merged commit 98a6a5b into main Aug 15, 2026
2 checks passed
@khaliqgant
khaliqgant deleted the docs/lintscopes-shipped branch August 15, 2026 20:49
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