triage-follow-ups

Classify GitHub issues by staleness, relevance, and documentation status.

Updated Apr 22, 2026

Search Tags:#automation #github #issue triage #workflows #backlog management

Ready to run

npx skills add https://github.com/aditrioka/nearyou-id --skill triage-follow-ups

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: triage-follow-ups
Source: https://github.com/aditrioka/nearyou-id/tree/main/.claude/skills/triage-follow-ups
Command: npx skills add https://github.com/aditrioka/nearyou-id --skill triage-follow-ups

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the triage process of GitHub issues, ensuring that open follow-up issues are accurately categorized and managed, reducing manual effort and preventing stale issues.

Core Features & Use Cases

Automated Issue Triage: Classifies open issues as silently-resolved, superseded, ready for documentation, still-valid, or in-progress.
Batch Decision Making: Allows batch decisions for closing, migrating, or promoting issues based on automated classifications.
Concurrent Sweep Coordination: Enables multiple concurrent sweeps to process different sets of issues without conflict.

Quick Start

Execute the triage-follow-ups skill to review and manage open 'follow-up' issues in your GitHub repository.

Frequently Asked Questions about triage-follow-ups

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

FAQPage Schema

How do I automate GitHub issue triage for stale backlog management?▼

Automating GitHub issue triage involves classifying open follow-up issues by staleness and relevance, allowing batch decisions to close, migrate, or promote issues automatically. This reduces manual backlog management effort and prevents stale issues.

What categories are used when classifying open GitHub follow-up issues?▼

Classifying open GitHub follow-up issues involves categorizing them as silently-resolved, superseded, ready for documentation, still-valid, or in-progress. This classification directly drives automated batch decisions for backlog management.

Can I process multiple GitHub issue sets simultaneously during an automated triage sweep?▼

Yes, concurrent sweep coordination enables processing multiple sets of GitHub issues simultaneously without conflict. This allows automated triage workflows to handle different backlog groups concurrently for faster issue management.

What's the best way to handle stale GitHub issues that are already resolved but still open?▼

Handling silently-resolved stale GitHub issues involves automated triage classification followed by batch decisions to close them. This workflow ensures accurate backlog management without manual review of each resolved issue.

Does this automated triage workflow require any specific GitHub workflow dependencies?▼

No external dependencies are required to run this automated GitHub issue triage workflow. It operates independently to classify issues and execute batch decisions for closing, migrating, or promoting follow-up items.