How do I install the Consolidate Issues skill?

Run npx skillmds@latest add majiayu000/consolidate-issues in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Consolidate Issues safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Consolidate Issues?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Consolidate Issues free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Consolidate Issues?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Consolidate Issues by majiayu000 — Agent Skill

Name: Consolidate Issues
Rating: 4.2 (5 reviews)
Author: majiayu000

Consolidate Issues

Reduce GitHub issue backlog through deduplication, linking, and closure. Use before creating new issues, when enforcement_mode is CONSOLIDATION, when issue:PR ratio exceeds 3:1, when AI-created issues reach 25, or when total issues approach 50.

majiayu000 Updated Sep 21, 2026 567 repo stars

File contents

Reduces issue backlog to prevent AI-created issue spam and maintain healthy project hygiene.

When to Use This Skill

Before creating any new GitHub issue (always check limits first)
When preflight returns enforcement_mode: CONSOLIDATION
When issue:PR ratio exceeds 3:1
When AI-created issues reach 25
When total open issues approach 50
Proactively during maintenance cycles

Enforcement Modes

Mode	Trigger	Action
NORMAL	All limits OK	Work normally
CONSOLIDATION	AI-created >= 25 or ratio > 3	Run this skill first
PR_CREATION	Ratio > 5, PRs < 3	Create PRs, not issues
PR_FOCUS	Open PRs >= 10	Resolve PRs only
PAUSED	Total issues >= 50	Run skipped entirely

Hard Limits

50 total issues: Run paused
25 AI-created issues: Skip issue creation
10 open PRs: PR_FOCUS mode
3:1 ratio: CONSOLIDATION mode

Consolidation Workflow

Step 1: Check Current Counts

TOTAL=$(gh issue list --state open --json number | jq length)
AI=$(gh issue list --state open --label ai-created --json number | jq length)
PRS=$(gh pr list --state open --json number | jq length)
RATIO=$(echo "scale=1; $TOTAL / ($PRS + 1)" | bc)
echo "Total: $TOTAL, AI: $AI, PRs: $PRS, Ratio: $RATIO:1"

Step 2: Fetch All Open Issues

gh issue list --state open --limit 100 --json number,title,body,labels,createdAt

Step 3: Close Duplicates

Identify duplicate issues. For each duplicate issue number, run the following commands as separate tool calls:

For issue #123:

gh issue edit 123 --add-label duplicate
gh issue close 123 --reason "not planned" \
  --comment "Duplicate of #456. Closing."

For issue #124:

gh issue edit 124 --add-label duplicate
gh issue close 124 --reason "not planned" \
  --comment "Duplicate of #456. Closing."

Step 4: Close Resolved Issues

Search for issues fixed by merged PRs:

gh pr list --state merged --limit 50 --json number,title,body

For each issue resolved by a merged PR, run the following command as a separate tool call:

gh issue close 456 --reason completed \
  --comment "Resolved by PR #789."

Step 5: Link Related Issues

For related (non-duplicate) issues, run the following command as a separate tool call for each related issue pair:

gh issue comment 123 --body "Related to #456."

For 3+ related issues, create an umbrella issue as a separate tool call.

Step 6: Report Summary

Document consolidation results:

Duplicates closed: N
Issues resolved by merged PRs: K
Related issues linked: M

Best Practices

Check before creating - Always verify limits first
Close aggressively - When in doubt, close as duplicate/resolved
Report to Slack - Never create issues for status updates
Focus on PRs - PRs close issues; issues don't close themselves

---name: consolidate-issuesdescription: Reduce GitHub issue backlog through deduplication, linking, and closure. Use before creating new issues, when enforcement_mode is CONSOLIDATION, when issue:PR ratio exceeds 3:1, when AI-created issues reach 25, or when total issues approach 50.---Reduces issue backlog to prevent AI-created issue spam and maintain healthy project hygiene.## When to Use This Skill- Before creating any new GitHub issue (always check limits first)- When preflight returns `enforcement_mode: CONSOLIDATION`- When issue:PR ratio exceeds 3:1- When AI-created issues reach 25- When total open issues approach 50- Proactively during maintenance cycles## Enforcement Modes| Mode | Trigger | Action || ------ | --------- | -------- || NORMAL | All limits OK | Work normally || CONSOLIDATION | AI-created >= 25 or ratio > 3 | Run this skill first || PR_CREATION | Ratio > 5, PRs < 3 | Create PRs, not issues || PR_FOCUS | Open PRs >= 10 | Resolve PRs only || PAUSED | Total issues >= 50 | Run skipped entirely |## Hard Limits- **50 total issues**: Run paused- **25 AI-created issues**: Skip issue creation- **10 open PRs**: PR_FOCUS mode- **3:1 ratio**: CONSOLIDATION mode## Consolidation Workflow### Step 1: Check Current Counts```bashTOTAL=$(gh issue list --state open --json number | jq length)AI=$(gh issue list --state open --label ai-created --json number | jq length)PRS=$(gh pr list --state open --json number | jq length)RATIO=$(echo "scale=1; $TOTAL / ($PRS + 1)" | bc)echo "Total: $TOTAL, AI: $AI, PRs: $PRS, Ratio: $RATIO:1"```### Step 2: Fetch All Open Issues```bashgh issue list --state open --limit 100 --json number,title,body,labels,createdAt```### Step 3: Close DuplicatesIdentify duplicate issues. For each duplicate issue number, run the following commands as separate tool calls:**For issue #123:**```bashgh issue edit 123 --add-label duplicategh issue close 123 --reason "not planned" \ --comment "Duplicate of #456. Closing."```**For issue #124:**```bashgh issue edit 124 --add-label duplicategh issue close 124 --reason "not planned" \ --comment "Duplicate of #456. Closing."```### Step 4: Close Resolved IssuesSearch for issues fixed by merged PRs:```bashgh pr list --state merged --limit 50 --json number,title,body```For each issue resolved by a merged PR, run the following command as a separate tool call:```bashgh issue close 456 --reason completed \ --comment "Resolved by PR #789."```### Step 5: Link Related IssuesFor related (non-duplicate) issues, run the following command as a separate tool call for each related issue pair:```bashgh issue comment 123 --body "Related to #456."```For 3+ related issues, create an umbrella issue as a separate tool call.### Step 6: Report SummaryDocument consolidation results:- Duplicates closed: N- Issues resolved by merged PRs: K- Related issues linked: M## Best Practices1. **Check before creating** - Always verify limits first2. **Close aggressively** - When in doubt, close as duplicate/resolved3. **Report to Slack** - Never create issues for status updates4. **Focus on PRs** - PRs close issues; issues don't close themselves

Frequently asked questions