| name | bonedigger |
| version | 1.1 |
| last_updated | 2026-08-08 |
| id | bonedigger |
| one_line_purpose | Operate bonedigger and kubestellar-bot issue/report automation. |
| entry_point | docs/skills/bonedigger/SKILL.md |
| category | ci-ops |
| mcp_compliance_level | partial |
| optimization_status | draft |
| status | active |
| dependencies | [] |
| tags | ["bonedigger","triage","automation"] |
| description | bonedigger + kubestellar-bot lifecycle automation. Use when working on ujust report, issue lifecycle, priority escalation, or how fixes ship back to images. |
| metadata | {"type":"reference"} |
bonedigger & kubestellar-bot
Repo: https://github.com/projectbluefin/bonedigger
When to Use
Use when changing ujust report, its confirmation flow, bonedigger intake, or
the labels that route user reports into the factory.
When Not to Use
Do not use this skill for generic GitHub issue triage, unrelated GitHub CLI
configuration, or lifecycle automation owned by projectbluefin/actions.
Core Process
- Keep collection local, targeted, bounded, and redacted.
- Route bugs from the booted image and feature requests to common.
- Preview the exact public payload and require consent before any upload.
- Submit with authenticated
gh, preserve failures as resumable drafts, and
verify the target, queue label, and receipt.
Red Flags
- Collecting diagnostics before the user selects an intent.
- Uploading a gist or creating an issue before preview and explicit consent.
- Applying both queue labels, using
machine-id, or reviving generic OTel
capture.
- Falling back to a browser issue form or a QR login flow.
Verification
References
