fix-stale-issues

Remove lifecycle/stale labels from linked telco-bot tracking issues via GitHub comments.

2|Updated Jul 8, 2024
One-click install
npx skills add https://github.com/redhat-best-practices-for-k8s/telco-bot --skill fix-stale-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-stale-issues
Source: https://github.com/redhat-best-practices-for-k8s/telco-bot/tree/main/.claude/skills/fix-stale-issues
Command: npx skills add https://github.com/redhat-best-practices-for-k8s/telco-bot --skill fix-stale-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Remove the lifecycle/stale label from tracking issues linked in telco-bot tracking issues by automating label cleanup.

Core Features & Use Cases

  • Linked-issue discovery: scans tracking issues in redhat-best-practices-for-k8s/telco-bot to identify any linked GitHub issues.
  • Stale-label remediation: for each linked issue that is open and labeled lifecycle/stale, posts a /remove-lifecycle stale comment to trigger label removal.
  • Targeted and broad cleanup: can operate on a specific issue when provided as an argument or on all open tracking issues when no argument is given.
  • Audit-ready reporting: produces a summary of actions taken and issues updated for traceability.

Quick Start

Run the fix-stale-issues 39 to fix a specific tracking issue or run the command without an argument to process all open tracking issues.

Frequently Asked Questions about fix-stale-issues

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

FAQPage Schema
How do I automatically remove stale labels from linked GitHub issues?

To remove stale labels automatically, you can run a command that scans tracking issues and posts a /remove-lifecycle stale comment on each linked issue to trigger label removal via GitHub MCP tools.

Can I clean up stale labels on a specific GitHub tracking issue instead of all of them?

Yes, you can clean up a specific tracking issue by providing its issue number as an argument, which limits the operation to that single issue instead of scanning all open tracking issues.

How does the stale label remediation process find linked issues in tracking issues?

The remediation process finds linked issues by scanning all open tracking issues for a linked issues table, then identifying any open GitHub issues labeled lifecycle/stale for automated comment posting.

Do I need to manually comment on each GitHub issue to remove the lifecycle stale label?

No, you do not need to manually comment. The workflow automates this by reading the tracking issues and posting the /remove-lifecycle stale comment on each linked issue that requires label cleanup.

What happens after removing stale labels from tracking issues?

After removing stale labels, the workflow produces an audit-ready summary report of actions taken and issues updated, ensuring traceability and visibility into the automated label cleanup process.