ワンクリックで
issue-triage
Triage new and updated GitHub issues on ric03uec/clawrium — apply type/complexity/area labels and draft a planning file.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Triage new and updated GitHub issues on ric03uec/clawrium — apply type/complexity/area labels and draft a planning file.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Cut a new clawrium release — bump version, sync docs, tag, trigger PyPI publish
Record a CLI demo (GIF or MP4) using VHS, with storyboard support for long-form / YouTube demos
Watch ric03uec/clawrium release tags; draft a short blog post per user-visible feature as a PR against blog/.
Detect user-visible changes from the last 24h of commits on main and propose doc and scenario updates as PRs.
Execute the plan for an issue (parent or subtask)
Know the clawctl CLI and manage your Clawrium fleet (hosts, agents, providers, channels, integrations, skills, secrets)
| name | issue-triage |
| description | Triage new and updated GitHub issues on ric03uec/clawrium — apply type/complexity/area labels and draft a planning file. |
| version | 0.1.0 |
| license | MIT |
| author | clawrium |
| platforms | ["linux","macos"] |
| metadata | {"cadence":"every 10 minutes","trigger":"poll","outputs":["labels","pull-request"]} |
Triage incoming work on ric03uec/clawrium. Run on a 10-minute poll cycle.
The loop is: find issues that need triage → read them carefully → apply
labels → draft a planning file as a PR.
For each candidate issue:
needs-triage is absent or the issue already
has a type:* label).LABELS.md for the allowed taxonomy. Do not invent labels.Candidates are issues opened or updated in the last 15 minutes (giving the poll a 5-minute overlap so nothing is missed during a slow run). Use:
gh issue list --repo ric03uec/clawrium \
--search "sort:updated-desc updated:>$(date -u -d '15 minutes ago' +%Y-%m-%dT%H:%M:%SZ)" \
--json number,title,body,labels,updatedAt
LABELS.md. At minimum: one
type:*, one complexity:*, one area:*. Add needs-review when
the issue lacks a clear Definition of Done..itx/active/<issue-number>/plan.md with a one-page
scaffold (Outcome / Approach / Files / Risk). Title:
chore(triage): draft plan for #<n>. Body links to the issue.agent-ready label. The PAT denies it; even if it
did not, this label is a human decision.main or merge a PR. PRs target main
with a feature branch named triage/<issue-number>-<slug>.needs-review and
leave a single short comment asking for Outcome + Definition of Done.
Do not invent requirements.LABELS.md is missing or unreadable, stop and post a [ITX-STUCK]
comment on the issue rather than guessing label names.type:* label — assume a
human or earlier triage decided. Touch only the missing dimensions..itx/active/<n>/plan.md that exceeds one page. The plan
is a starting point for /itx:plan-create, not a substitute for it.