issue-patrol

Scan, triage, and resolve open GitHub issues with automated pull requests.

89|17|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/statsclaw/statsclaw --skill issue-patrol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-patrol
Source: https://github.com/statsclaw/statsclaw/tree/main/skills/issue-patrol
Command: npx skills add https://github.com/statsclaw/statsclaw --skill issue-patrol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually scanning, triaging, and fixing open GitHub issues is time-consuming and inconsistent, especially for repositories with frequent bug reports. This skill automates the entire end-to-end workflow to reduce manual overhead and speed up issue resolution for development teams.

Core Features & Use Cases

  • Automated Issue Scanning & Triage: Fetches all open issues from a target GitHub repository and classifies them as actionable (bugs, test failures, errors) or non-actionable (feature requests, questions, discussions) based on content.
  • Prioritized Fix Loop: Orders actionable issues by severity (crashes > test failures > warnings > minor bugs) and runs the full isolated StatsClaw development workflow (planner → builder → tester → reviewer → shipper) to generate, test, and push fixes for each issue.
  • Auto-Reporting & Communication: Generates a patrol summary report and automatically posts comments on fixed issues linking to pull requests, with no manual intervention required for standard bug fixes. Use case: For a statistical software repository with dozens of open bug reports, run this skill to automatically fix low-severity crashes and test failures, open PRs, and notify issue authors of the fixes.

Quick Start

Use the issue-patrol skill to scan open issues in the xuyiqing/fect repository, fix all actionable bugs, and push fixes to the cfe branch.

Frequently Asked Questions about issue-patrol

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

FAQPage Schema
How do I automate GitHub issue triage and bug fixes for my repository?

Automated issue triage classifies open GitHub issues as actionable bugs or non-actionable feature requests based on their content. It then orders actionable issues by severity, prioritizing crashes over test failures, warnings, and minor bugs to determine the fix execution loop sequence.

Can I automatically create pull requests for GitHub bug reports?

Yes, you can automatically resolve test failures by running an automated fix loop that executes planner, builder, tester, reviewer, and shipper stages. This isolated workflow targets test failures after crashes in the severity order, generating tested fixes and opening pull requests without manual intervention.

How does automated issue scanning handle feature requests and discussions?

Automated issue scanning handles feature requests and discussions by classifying them as non-actionable and excluding them from the fix loop. It targets actionable bugs and recurring test failures, so feature requests and general discussions are ignored to prevent unintended code changes.

Do I need manual coordination to push automated bug fixes to a specific branch?

No, you do not need manual coordination to push automated bug fixes to a specific branch. The skill runs an isolated development workflow that automatically generates, tests, and pushes fixes to your designated target branch and creates pull requests.