bulk-issues

Automate bulk resolution of open GitHub issues on a single feature branch.

1|1|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/laststance/skills --skill bulk-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bulk-issues
Source: https://github.com/laststance/skills/tree/main/skills/bulk-issues
Command: npx skills add https://github.com/laststance/skills --skill bulk-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bulk issue management: processes, tests, and merges for multiple issues on a single feature branch to streamline GitHub workflows.

Core Features & Use Cases

  • Single-branch resolution: handles multiple issues on one feature branch with a unified commit strategy.
  • Mandatory verification gates: ensures lint, typecheck, unit tests, E2E, and build before merging.
  • CodeRabbit review loop: iterates reviews until CI passes and PR is merged.

Quick Start

Run the bulk-issues invocation to process all open issues on a feature branch and consolidate changes into a single PR.

Frequently Asked Questions about bulk-issues

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

FAQPage Schema
How do I resolve multiple GitHub issues on a single feature branch?

You can resolve multiple GitHub issues on a single feature branch by automating a 5-phase task workflow that handles triage, planning, implementation, verification, and merge into one consolidated PR.

What's the best way to automate bulk issue triage and code review in CI?

Automating bulk issue triage and code review requires applying mandatory verification gates like lint, typecheck, and tests, then iterating CodeRabbit review loops until CI passes and the PR merges.

Can I consolidate multiple issue fixes into one PR without skipping verification gates?

Yes, you can consolidate multiple issue fixes into one PR by applying a unified commit strategy that enforces lint, typecheck, unit tests, E2E, and frontend build verification before merging.

Does bulk issue management work with strict CodeRabbit review loops?

Bulk issue management works with strict CodeRabbit review loops by iterating automated reviews until CI passes, ensuring every consolidated fix on the feature branch meets PR merge criteria.

Why does my multi-issue feature branch fail CI before merge?

A multi-issue feature branch fails CI before merge if it skips mandatory verification gates; you must ensure every issue passes lint, typecheck, unit tests, E2E, and frontend build verification.

When should I avoid consolidating issue resolution onto one branch?

You should avoid consolidating issue resolution onto one branch when issues require independent deployment timelines or conflicting code changes that cannot pass unified lint, typecheck, and test gates.