docs(agents): document agent label checklist when opening a PR

[castrojo]

Agents were not updating labels after opening a PR, leaving issues appearing unclaimed in the queue.

Add one-liner to the issue lifecycle section: when an agent opens a PR, remove queue/agent-ready from the issue and add queue/claimed to both issue and PR.

Assisted-by: Claude Sonnet 4.6 via GitHub Copilot

[coderabbitai]

Warning

Review limit reached

@castrojo, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 29 minutes and 51 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

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.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: dc75e122-1b64-46d0-bda8-c75432391069

📥 Commits

Reviewing files that changed from the base of the PR and between 3284cfe and e0a4c6c.

📒 Files selected for processing (4)

• .github/workflows/bonedigger.yml
• .github/workflows/hive-status-sync.yml
• AGENTS.md
• docs/skills/hive-review.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/agent-label-workflow

---

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.}

[hanthor]

bonedigger.yml calls a reusable workflow pinned to @main with secrets: inherit:
uses: projectbluefin/bonedigger/.github/workflows/lifecycle.yml@main

Any future push to projectbluefin/bonedigger's main branch will run with access to all secrets in this repo. Pin to a specific commit SHA to prevent unintended changes from automatically inheriting those permissions.

Also: PR #391 adds the same two workflow files. Close #391 before merging this one to avoid a merge conflict.

[castrojo]

LGTM — can't self-approve (castrojo authored), flagging for 2nd review.

• bonedigger.yml: correct event triggers (issues + issue_comment + daily schedule); minimal permissions (issues:write + contents:read); secrets: inherit is correct for reusable workflow
• hive-status-sync.yml: Python inline script is robust — regex extraction of agents JSON, health bar, relative time, CI status, issue counts, fireteam detection; GraphQL writes use PROJECT_TOKEN, reads use github.token — correct scoping; workflow_dispatch + push to main + hourly schedule is right
• AGENTS.md: label checklist line is accurate per the issue lifecycle documented in the custom instructions
• docs/skills/hive-review.md: good session reference; content aligns with ~/src/skills/hive-review/SKILL.md

Note: PR #391 covers only the two workflow files (subset of this PR). Recommend closing #391 in favor of this one.

[hanthor]

Two blocking issues remain:

1. Both #391 and #393 add identical .github/workflows/bonedigger.yml and .github/workflows/hive-status-sync.yml, so whichever lands second will conflict unless one PR drops those workflow files.
2. bonedigger.yml still uses projectbluefin/bonedigger/.github/workflows/lifecycle.yml@main with secrets: inherit. Please pin that reusable workflow to a specific commit SHA before merging.