issues_loop

Monitor GitHub open issues periodically and trigger flutter-work-flow after closing each.

5|3|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/ZHLX2005/fr --skill issues-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issues_loop
Source: https://github.com/ZHLX2005/fr/tree/main/.claude/skills/issues_loop
Command: npx skills add https://github.com/ZHLX2005/fr --skill issues-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates periodic monitoring and resolution of GitHub open issues, reducing manual triage overhead and accelerating issue closure.

Core Features & Use Cases

  • Periodic open-issues monitoring: runs every few minutes to check for new or existing open issues in a repository.
  • Automated workflow trigger: after closing issues, it triggers flutter-work-flow to propagate the result.
  • Recurring scheduling guidance: enforces cron-based recurring scheduling to sustain continuous automation.

Quick Start

Set up CronCreate with recurring: true to run every 5 minutes and automatically process and close open issues.

Frequently Asked Questions about issues_loop

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

FAQPage Schema
How do I automate GitHub issue triage on a recurring schedule?

You can automate GitHub issue triage by configuring a recurring cron job to run every 5 minutes. This recurring schedule retrieves open issues via gh issue list and automatically processes and closes them to reduce manual overhead.

What is the best way to auto-close GitHub issues and trigger a workflow?

The best way to auto-close GitHub issues and trigger a workflow is using an automated monitoring routine that closes open issues and subsequently pushes a flutter-work-flow to propagate the closure result.

Can I use cron scheduling to periodically monitor GitHub repositories for open issues?

Yes, you can use cron scheduling to periodically monitor GitHub repositories. By enforcing a recurring cron schedule, the system continuously checks for new and existing open issues every few minutes for sustained automation.

Does automated issue closure work with a flutter-work-flow deployment pipeline?

Yes, automated issue closure works with a flutter-work-flow deployment pipeline. After the automated routine closes monitored open issues, it explicitly triggers and pushes the flutter-work-flow to propagate the results downstream.

Do I need any external dependencies to set up recurring GitHub issue monitoring?

No external dependencies are required to set up recurring GitHub issue monitoring. The automation relies entirely on built-in capabilities like CronCreate for scheduling and gh issue list for retrieving open issues from your repositories.