hotplex-issue-manager

Converts multiple GitHub issues into a merged pull request with ROI-prioritized, conflict-checked selections.

47|15|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/hrygo/hotplex --skill hotplex-issue-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hotplex-issue-manager
Source: https://github.com/hrygo/hotplex/tree/main/.agents/skills/hotplex-issue-manager
Command: npx skills add https://github.com/hrygo/hotplex --skill hotplex-issue-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns a messy set of GitHub issues into a single, coherent merge-ready Pull Request, reducing merge conflicts, review fatigue, and duplicate work that often happens in the one-issue-one-PR workflow.

Core Features & Use Cases

  • Phase-based workflow with user confirmation: performs analysis/verification, ROI scoring, PR conflict checks, and then implementation—pausing for approval between phases.
  • ROI-driven prioritization: scores issues by impact, urgency, and effort to recommend which issues to include in the batch.
  • Batch coherence and conflict avoidance: groups selection to maximize thematic consistency and excludes issues already covered by existing PRs or overlapping diffs to prevent conflicts.
  • GitHub issue → PR delivery: can fetch up to 100 open issues, produce ranked outputs, generate an implementation plan, implement changes with conventional commits, and deliver one PR that closes multiple issues.

Quick Start

Ask the AI: "Analyze HotPlex open issues and deliver the highest-priority fixes as a single PR."

Frequently Asked Questions about hotplex-issue-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I combine multiple GitHub issues into a single pull request?

To combine multiple GitHub issues into a single pull request, this Skill analyzes related issues, applies ROI prioritization, checks for diff conflicts, and batches the fixes into one merge-ready PR using conventional commits.

What is the best way to batch GitHub issues for a Go repository maintenance workflow?

Batching GitHub issues for Go repository maintenance is best handled by grouping 2-5 related module issues, scoring them by impact and effort, and delivering one consolidated PR that passes test, lint, and build verification.

Can I prioritize GitHub issues by ROI before creating a pull request?

Yes, you can prioritize GitHub issues by ROI before creating a pull request. The workflow scores open issues based on impact, urgency, and effort to recommend the highest-value batch for implementation.

How do I avoid merge conflicts when batching multiple GitHub issues into one PR?

To avoid merge conflicts when batching GitHub issues into one PR, the workflow checks existing PRs and excludes issues with overlapping diffs to ensure thematic consistency and prevent code conflicts.

Do I need GitHub CLI access to batch issues into a merge-ready pull request?

Yes, you need GitHub CLI access to batch issues into a merge-ready pull request. The deterministic multi-phase workflow requires it to fetch open issues, execute changes, and verify repository tests and builds.