__maintain-issues

Detect close candidates, validate labels, auto-check checkboxes, and find duplicate issues.

Updated May 13, 2026
One-click install
npx skills add https://github.com/cilly-yllic/.llm --skill maintain-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: __maintain-issues
Source: https://github.com/cilly-yllic/.llm/tree/main/skills/ja/__maintain-issues
Command: npx skills add https://github.com/cilly-yllic/.llm --skill maintain-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you maintain repository issue hygiene by automatically identifying which open issues should be closed, which labels are incorrect, which checkboxes can be marked complete, and which issues are likely duplicates.

Core Features & Use Cases

  • Close-candidate detection: Finds resolved or unnecessary issues using signals such as merged PRs, resolution comments, checkboxes completion, closing-related labels, and stale updates.
  • Label validity checks: Detects missing, excessive, or incorrect labels and proposes safe add/remove changes without creating new labels.
  • Checkbox auto-checking: Proposes updates to checklist items when completion is evidenced by commits, PRs, or comments.
  • Duplicate issue detection: Groups similar issues and proposes merge, close, or keep decisions.

Use cases include doing periodic maintenance before releases, reducing issue backlog clutter, and keeping label/checkbox conventions consistent across teams.

Quick Start

Run the skill to perform a full maintenance pass on all open issues by using the command: /__maintain-issues

Frequently Asked Questions about __maintain-issues

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

FAQPage Schema
How do I triage open GitHub issues to find candidates for closing?

Issue triage detects close candidates by analyzing merged PRs, resolution comments, completed checkboxes, closing-related labels, and stale updates. It performs a staged maintenance pass on all open issues to identify which ones should be closed.

What is the best way to detect duplicate issues in a repository backlog?

Duplicate issue detection groups similar open issues and proposes merge, close, or keep decisions. It analyzes issue content to find matches across the backlog, enabling optional corrective actions to reduce clutter.

Can I automatically validate and fix incorrect labels on open issues?

Label validity checks detect missing, excessive, or incorrect labels on open issues. The skill proposes safe add or remove changes without creating new labels, keeping label conventions consistent across teams.

How do checkbox automation and auto-checking work for issue maintenance?

Checkbox auto-checking proposes updates to checklist items when completion is evidenced by commits, PRs, or comments. It scans open issues for these signals and marks checkboxes complete to maintain accurate issue tracking.

Do I need to manually confirm destructive operations during issue triage?

Destructive operations require user confirmation before execution. The skill supports step-level skipping via flags to safely control scope, ensuring no issue closures, label changes, or checkbox updates happen without explicit approval.

Does issue triage work with different issue backends or only GitHub?

Issue triage applies across different issue backends by first inferring the configured service and then executing the staged maintenance process. It adapts to the repository's specific backend to perform close-candidate detection and label validation.