Fix GitHub issues using subagent-driven-development with parallel execution where appropriate. Triggers: fix issue, github issue, issue resolution, subagent development, parallel execution, issue workflow, gh issue, fix github Use when: addressing GitHub issues systematically, multiple related issues need fixing, tasks can be parallelized across subagents, quality gates needed between task batches DO NOT use when: single simple fix - just implement directly. DO NOT use when: issue needs clarification - comment first to clarify scope. Uses subagents for parallel execution with code review gates between batches.
/plugin marketplace add athola/claude-night-market/plugin install pensive@claude-night-marketThis skill inherits all available tools. When active, it can use any tool Claude has access to.
modules/completion.mdmodules/issue-discovery.mdmodules/parallel-execution.mdmodules/quality-gates.mdmodules/task-planning.mdmodules/troubleshooting.mdRetrieves GitHub issue content and uses subagent-driven-development to systematically address requirements, executing tasks in parallel where dependencies allow.
| Phase | Description | Module |
|---|---|---|
| 1. Discovery | Parse input, fetch issues, extract requirements | issue-discovery |
| 2. Planning | Analyze dependencies, create task breakdown | task-planning |
| 3. Execution | Dispatch parallel subagents for independent tasks | parallel-execution |
| 4. Quality | Code review gates between task batches | quality-gates |
| 5-6. Completion | Sequential tasks, final review, issue updates | completion |
fix-issue:discovery-completefix-issue:tasks-plannedfix-issue:parallel-batch-completefix-issue:review-passedfix-issue:sequential-completefix-issue:issues-updated# Fetch issue details
gh issue view <number> --json title,body,labels,comments
# Add completion comment
gh issue comment <number> --body "message"
# Close issue
gh issue close <number> --comment "reason"
fix_issue:
parallel_execution: true
max_parallel_subagents: 3
review_between_batches: true
auto_close_issues: false
commit_per_task: true
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.