github-issues-resolved

Automates GitHub issue triage, parallel fixes, code review, and merging via sub agents.

1|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/360org/vuaassistant --skill github-issues-resolved-360org
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-issues-resolved
Source: https://github.com/360org/vuaassistant/tree/main/.claude/skills/github-issues-resolved
Command: npx skills add https://github.com/360org/vuaassistant --skill github-issues-resolved-360org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually triaging, fixing, reviewing, and merging GitHub issues one by one is slow and error-prone. This Skill orchestrates a multi-agent workflow that scans open issues, fixes them in parallel inside isolated git worktrees, reviews each fix, and merges approved changes automatically. ## Core Features & Use Cases - Issue Scanning & Classification: Fetches open issues via the GitHub CLI, filters by issue number or label, and assigns priority (high/medium/low) based on labels and content. - Parallel Fixing in Isolated Worktrees: Spawns one sub agent per issue, each working in its own git worktree to avoid conflicts, enforcing root-cause fixes with TypeScript checks (npx tsc --noEmit). - Mandatory Review Gate: Every fix is reviewed and scored 1-10; only fixes scoring 7 or higher are approved for merging. - Use Case: Run the skill with the label "bug" to automatically fix all open bug issues, receive a structured report of fixed, skipped, and rejected issues, then confirm before pushing to remote. ## Quick Start Ask the assistant to run the github-issues-resolved skill with a label like "bug" or an issue number to automatically scan, fix, review, and merge those GitHub issues.

Frequently Asked Questions about github-issues-resolved

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

FAQPage Schema
How do I automatically fix multiple GitHub issues at once?▼

Run the skill with no arguments to process all open issues, or pass a label like "bug" to filter. It spawns one sub agent per issue, each fixing in an isolated git worktree, then reviews and merges approved fixes.

How does the skill decide which GitHub issues to prioritize?▼

Issues are classified by priority using labels and body content: labels containing bug, critical, or security (or body text mentioning crash, error, broken) are high priority; enhancement or improvement labels are medium; everything else is low.

Does the skill push merged fixes to the remote repository?▼

No. The skill merges approved fixes into the local main branch only and waits for explicit user confirmation before pushing to the remote, as a safety rule.

What happens if a fix fails the code review?▼

Each fix receives a quality score from 1 to 10 during review. Fixes scoring below 7 are rejected and not merged; the final report lists rejected fixes with reasons and offers to retry.

Why would an issue be skipped instead of fixed?▼

Issues that are ambiguous or lack sufficient information are skipped with a recorded reason rather than guessed at. The final report asks the user to supply the missing details so the issue can be retried.