chore(skills): /feature claim flips board status to In progress#3830
chore(skills): /feature claim flips board status to In progress#3830PierreBrisorgueil wants to merge 1 commit into
Conversation
Phase 0.0 step 3b — best-effort call to infra's board-status.sh after a successful claim (bubbles sub-issue flips to the parent epic). Silent no-op off-machine / boardless org; /dev:roadmap in-progress-sync is the safety net.
|
Warning Review limit reached
More reviews will be available in 25 minutes and 59 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the 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 include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Pull request overview
Updates the /feature #N claim flow documentation so that, after assigning yourself and posting the canonical WIP comment, the skill makes a best-effort call into the infra board-status.sh helper to set the related GitHub Project board item to In progress.
Changes:
- Add Phase 0.0 step 3b to flip the issue (and parent epic, if applicable) to In progress via
infra/marketplace/shared/board-status.sh. - Document that the board update is explicitly best-effort and must not block the claim flow.
| _bs=/Users/pierrebrisorgueil/Documents/Dev/github/pierreb-projects/infra/marketplace/shared/board-status.sh | ||
| [ -f "$_bs" ] && bash "$_bs" "$(gh repo view --json nameWithOwner -q .nameWithOwner)#<N>" "In progress" || true |
| [ -f "$_bs" ] && bash "$_bs" "$(gh repo view --json nameWithOwner -q .nameWithOwner)#<N>" "In progress" || true | ||
| ``` | ||
|
|
||
| Best-effort by design: script missing (machine without the infra checkout), org without a board (comes/montaine), or issue not yet on the board → silent no-op; `/dev:roadmap` in-progress-sync is the safety net. Never set Ready or Done from here. |
|
Closing — this leaks personal-environment details into an open-source stack: a hardcoded home-dir path and a reference to a private infra board-automation script. Board-status automation belongs in private infra, not the open-source /feature skill. Reverting. |
Summary
.claude/skills/feature/SKILL.md— after a successful/feature #Nclaim (assignee set + WIP comment posted), a best-effort call toinfra/marketplace/shared/board-status.shflips the corresponding GitHub Project board item to In progress.58a076c(pierreb-projects/infra) shipsboard-status.sh; this PR wires the call into the Node/featureskill. Phase 0.0 step 3b is best-effort: silent no-op when running off-machine or in a boardless org, so the claim flow is never blocked./dev:roadmapin-progress-sync remains the safety net for any gaps.Scope
.claude/skills/feature/SKILL.md(docs/skill only)nonelowValidation
npm run lint— N/A (markdown only, no code changed)npm test— N/A (no code changed)board-status.shinterfaceGuardrails check
.env*,secrets/**, keys, tokens)Notes for reviewers
pierreb-devkit/Vue).board-status.shscript is best-effort by design: it exits 0 silently if the infra repo is not accessible or the project board is not configured, so downstream projects are never affected.