Stats
Actions
Tags
From cc-godmode
Loads a GitHub issue, analyzes its type/complexity/areas, selects a workflow, executes agents, and creates a PR referencing the issue.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cc-godmode:issue-processingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
```
"Process Issue #X"
1. @github-manager loads issue #X from GitHub
↓
2. Orchestrator analyzes issue:
↓
3. Select & execute appropriate workflow
↓
4. @github-manager creates PR with "Fixes #X"
When analyzing a loaded issue, determine:
| Dimension | Options | How to Determine |
|---|---|---|
| Type | Bug / Feature / Enhancement / Docs | Issue labels, title keywords, description |
| Complexity | Low / Medium / High | Scope of changes, number of files, dependencies |
| Areas | API / UI / Backend / Infrastructure / Docs | File paths mentioned, components affected |
| API Impact | Yes / No | Does it touch critical API paths? |
| Type | Complexity | Workflow |
|---|---|---|
| Bug | Any | Bug Fix workflow |
| Feature | Any | Feature workflow |
| Enhancement | Low | Bug Fix workflow |
| Enhancement | Medium/High | Feature workflow |
| Docs | Any | @scribe only |
| Any | Any + API Impact | API Change workflow |
The PR created by @github-manager MUST include:
| Label | Implication |
|---|---|
bug | Bug Fix workflow |
enhancement | Feature workflow |
api | API Change workflow (include @api-guardian) |
docs | Documentation only (@scribe) |
security | Force @validator security check |
performance | Add performance metrics to @tester |
urgent / hotfix | Emergency workflow (streamlined) |
npx claudepluginhub cubetribe/claudecode_godmode-onResolves GitHub issues via 8-phase workflow: fetch details, analyze requirements, implement solutions, verify correctness, code review, commit changes, create PRs. Activates on resolve, implement, fix requests or issue references.
Investigates GitHub issues and PRs: pulls, classifies, searches codebase for root cause, reviews contributed code, proposes fixes with file:line references, and optionally implements fixes.
Investigates and resolves GitHub issues with systematic triage, root cause analysis, test-driven fixes, and pull request management. Use when given an issue ID or URL.