القائمة
Analyze and triage issues — categorize, assess complexity, suggest approach. Use when: reviewing new issues, prioritizing backlog, or processing hub.issue relay events.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Manage tasks with bit issue — Git-native issue tracking without external services. Use when: creating tasks, tracking work items, organizing sub-issues, searching issues, or managing project workflow with bit.
Manage implementation sessions with bit issue coordination. Use when: starting non-trivial code changes, resuming previous work, entering plan mode, creating branches, or doing parallel work. Triggers on keywords: bit issue, session, parallel work, resume, continue.
Investigate and fix CI failures. Use when: debugging failed GitHub Actions runs, fixing build/test failures, or processing ci.status relay events.
Review code changes and provide structured feedback. Use when: reviewing PRs, analyzing code diffs for bugs/security/style, or processing review.request relay events.
Push results back to a bit relay room after completing a task. Use when: reporting CI status, submitting PR reviews, commenting on issues, or publishing agent responses via relay.
Synchronize bit issues and PRs across repositories via a relay server. Use when: coordinating with remote sessions, sharing issues between machines, syncing hub data across clones, or the user mentions relay, sync, remote coordination, or distributed issues.
| name | triage-issue |
| description | Analyze and triage issues — categorize, assess complexity, suggest approach. Use when: reviewing new issues, prioritizing backlog, or processing hub.issue relay events. |
Analyze and triage issues.
bit issue list --open shows untriaged issueshub.issue (optional, requires relay)bit issue get <id> (skip session:<branch> labeled issues — they are session-coordination records, not backlog)P0, P0.5, P1, P2, P3, P4) + area (merge, test, hub, perf, wasm, object, relay, sparse, …) + optional type (bug, edge-case, epic)## Triage: <issue-title>
**Type**: bug | feature | question | improvement
**Complexity**: small | medium | large
**Labels**: P1, merge, bug
**Area**: modules/bit_core, modules/bit/cmd/bit, modules/bitx_hub, etc.
## Analysis
Brief description of what needs to be done.
## Suggested approach
1. Step 1
2. Step 2
3. Step 3
# --label replaces the whole set: pass priority + area + type together
bit issue update <id> --label "P1" --label "merge" --label "bug"
bit issue comment add <id> --body "Triage: ..."