Skip to content

chore(skills): /feature Phase 0.0 — fetch issue body + aged-scope re-validation gate#4395

Open
PierreBrisorgueil wants to merge 2 commits into
masterfrom
chore/feature-intake-body-gate
Open

chore(skills): /feature Phase 0.0 — fetch issue body + aged-scope re-validation gate#4395
PierreBrisorgueil wants to merge 2 commits into
masterfrom
chore/feature-intake-body-gate

Conversation

@PierreBrisorgueil

Copy link
Copy Markdown
Collaborator

What

The Phase 0.0 claim step fetched number,title,state,assignees,comments — never the issue body, so the scope written in the description was silently ignored by the executor. It also implemented aged issues as-written even when the referenced code had moved.

  • fetch body + createdAt in the Phase 0.0 gh issue view call; the body is the primary scope source
  • new §4 aged-scope gate: old issue (createdAt > ~7 days) or references that no longer match the codebase → re-validate scope against current code, present drift before implementing; un-claim on abort
  • §Proceed renumbered to 5

Doc-only change to .claude/skills/feature/SKILL.md. Mirrors the same change in the sibling stack repo.

Closes #4394

…validation gate

The claim step read number,title,state,assignees,comments but never the
issue body, so the scope written in the description was silently ignored.
Add body to the fetch and a re-validation gate: an old issue (or one whose
references no longer match the codebase) gets its scope re-checked against
current code, with drift presented to the user before implementation.

Closes #4394
@coderabbitai

coderabbitai Bot commented Jul 2, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 55 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: d0e72828-ed64-4b43-a707-f91aa14017c8

📥 Commits

Reviewing files that changed from the base of the PR and between eb97682 and 5f7279b.

📒 Files selected for processing (1)
  • .claude/skills/feature/SKILL.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/feature-intake-body-gate

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.

Removing only the assignee left the WIP — comment behind, which step 2
treats as a resumable claim on the next run.
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.

🔧 /feature Phase 0.0: fetch the issue body + aged-scope re-validation

1 participant