feat(skill/feature): add Phase 0.0 issue claim-on-start

[PierreBrisorgueil]

Summary

• Add Phase 0.0 — Issue Claim section to /feature skill: when invoked with #N, auto-claims issue via assignee + timestamped WIP — comment
• Detection table catches cross-session collisions (other assignee, fresh WIP comment <24h, stale WIP >24h)
• Byte-identical mirror of pierreb-devkit/Node#3639 (already merged)

Test plan

• Smoke test on sandbox issue (pierreb-projects/infra#29, closed) — verified claim happens, resume path matches @me short-circuit
• Pre-push critical-review gate: /critical-review Claude backend → OK (0 findings, 97% confidence)
• Byte-identity vs Node version: zero diff confirmed

Refs pierreb-projects/infra#28
Mirror of pierreb-devkit/Node#3639

[coderabbitai]

Warning

Rate limit exceeded

@PierreBrisorgueil has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 54 minutes and 50 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 3a4b1d40-24fc-44a9-a049-915eb4e62471

📥 Commits

Reviewing files that changed from the base of the PR and between 5f8b539 and b15a369.

📒 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 feat/feature-skill-claim-on-start

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

Adds an “Issue Claim” preflight phase to the /feature Claude skill so that invoking /feature #N automatically establishes ownership (assignee + timestamped WIP — … comment) and detects cross-session collisions before proceeding into normal Phase 0 scope analysis.

Changes:

• Added Phase 0.0 “Issue Claim” flow that runs only when /feature is invoked with an issue number (#N).
• Defined collision-detection rules based on current assignee and most recent canonical WIP — comment (including <24h vs >24h handling).
• Standardized the claim action to (1) assign @me and (2) post a structured WIP comment including session id, branch name, and UTC timestamp.