菜单
Triage and prioritize GitHub issues by type (bug/feature/chore), complexity (S/M/L), and priority (P1-P4). Detect duplicates, propose execution order, and generate task graphs for godmode automation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | godmode:issue-triage |
| description | Triage and prioritize GitHub issues by type (bug/feature/chore), complexity (S/M/L), and priority (P1-P4). Detect duplicates, propose execution order, and generate task graphs for godmode automation. |
| requires | [] |
| next | ["task-management"] |
Systematically analyze open GitHub issues to establish priority, complexity, and task dependencies. Use before sprint planning or when the backlog is unclear.
| Type | Indicators | Priority Uplift |
|---|---|---|
| Bug | Error, crash, panic, "doesn't work", regression, breakage | +1 level |
| Feature | "Add support for", enhancement, new capability, API change | none |
| Chore | Docs, cleanup, refactoring, dependency bump, test coverage | none |
Decision tree:
| Size | Characteristics | Example |
|---|---|---|
| S | Single file, obvious fix, no design debate | Fix typo in README, bump version |
| M | Multi-file, some design, cross-module impact | Add a new CLI flag, refactor one module |
| L | Cross-crate, needs plan, requires RFC or design doc | New agent system, major API overhaul |
Time proxy: S ≈ 1–2 hours, M ≈ 1–2 days, L ≈ 1–2 weeks (before planning).
| Priority | Criteria | Action |
|---|---|---|
| P1 | Blocking (security, outage, data loss, high-rep user) | Start next |
| P2 | Important (frequent report, significant feature, team blockers) | Sprint in |
| P3 | Nice-to-have (incremental improvement, niche use case) | Backlog |
| P4 | Speculative (vague request, "someday", personal preference) | Consider later |
Application: Assign base priority from table, then apply type uplift (bugs +1 level), then consider user urgency/reputation.
Check for:
#<number> refs)Handling: Flag as related, group in triage output, recommend consolidation to user but do not merge without approval.
When converting triage to godmode tasks:
t1, t2, ...) or issue-number-based
(t42, t51, ...).Example:
# Bug (P1) — no deps
godmode task add "Fix panic on invalid UTF-8 input" \
--id t1 --crate-name parser --priority high
# Related feature — depends on bug fix
godmode task add "Add YAML support" \
--id t2 --depends-on t1 --crate-name parser
# Independent chore
godmode task add "Update README with examples" \
--id t3 --priority normal
# Fetch open issues and convert to tasks manually:
gh issue list --repo <owner/repo> --state open \
--json number,title,labels --limit 50
# Then add each as a task:
godmode task add "<title>" --id t<N> --crate-name <crate>
Note:
godmode task pull --github [--repo owner/repo] [--label <label>]imports open GitHub issues as tasks. Or usegh issue listand add tasks individually.
godmode task list # show all tasks
godmode status # show ready and runnable
godmode dispatch # emit parallel chains JSON
Produce a table with these columns:
| # | Title | Type | Size | Priority | Group | Order | Notes |
|---|-------|------|------|----------|-------|-------|-------|
Where:
#: GitHub issue numberTitle: Issue title (truncated to ~40 chars)Type: Bug, Feature, or ChoreSize: S, M, or LPriority: P1, P2, P3, or P4Group: Component or feature area (e.g., "Parser", "CLI", "Docs")Order: Suggested execution rank (1 = first)Notes: Duplicates, blockers, user reputation, or other contextExample:
| 42 | Panic on UTF-8 input | Bug | S | P2 | Encoding | 1 | User: @alice |
| 51 | Add YAML support | Feature | M | P3 | Parser | 3 | Deferred |
| 63 | Update docs | Chore | S | P3 | Docs | 4 | |
| 48 | Same as #42 — UTF-8 panic | Bug | S | P2 | Encoding | — | Duplicate |
gh auth status before running; fail gracefully if
repo is private or unreachable.# User: "Triage the issues in my repo"
# Agent runs:
gh issue list --repo <owner/repo> --state open \
--json number,title,body,labels,createdAt --limit 50
# Agent classifies each (manual inspection of title/body for type/complexity)
# Agent produces triage table
# User asks: "Create tasks for P1 and P2 issues"
# Agent runs:
for each P1/P2 issue:
godmode task add "<title>" --id t<N> --crate-name <crate> --priority high
# User runs:
godmode status # see new tasks
godmode dispatch # see parallel chains
Audit godmode skills, agents, and plugin files for internal consistency, broken references, stale commands, and cross-skill contradictions. Use when asked to "introspect", "audit the skills", "review godmode", or after adding new skills.
Use at the start of every conversation to orient to available skills and workspace rules. Replaces superpowers entirely. Triggers on session start, "/godmode", or "what skills do you have".
Generate and maintain a `.ctx/godmode/memory-bank/` directory that captures project context backed by source code. The memory bank is injected into prompts via lifecycle hooks and updated incrementally as work progresses. Use when starting a new project, onboarding to an unfamiliar codebase, or when context drift is detected.
Patterns and techniques for adding governance, safety, and trust controls to AI agent systems in Rust. Use this skill when building agents that call external tools, implementing policy-based access controls, adding semantic intent classification to detect dangerous prompts, creating trust scoring systems for multi-agent workflows, building audit trails, or enforcing rate limits and content filters. Covers policy composition, tool wrappers, trust decay, and JSONL audit trails — all in Rust.
Parse git history into structured changelogs. Use to generate release notes, audit commit conventions before tagging, or integrate with `godmode release` workflow.
Dead code detector for Rust workspaces. Finds unused public API surface, orphaned test helpers, stale feature flags, and plugin artifacts referencing removed CLI subcommands. Cross-references pub exports against call sites across the workspace.