kiln-analyze-issues

Categorize and label up to 50 open GitHub issues with closure and backlog suggestions.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/yoshisada/ai-repo-template --skill kiln-analyze-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiln-analyze-issues
Source: https://github.com/yoshisada/ai-repo-template/tree/main/plugin-kiln/skills/kiln-analyze-issues
Command: npx skills add https://github.com/yoshisada/ai-repo-template --skill kiln-analyze-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage open GitHub issues by categorizing, labeling, flagging actionable items, and offering closure suggestions with backlog creation via /kiln:kiln-report-issue.

Core Features & Use Cases

  • Automatically assign a primary category to each issue (skills, agents, hooks, templates, scaffold, workflow, or other) based on its content.
  • Apply the analyzed label and a category label to track progress and avoid re-processing, and propose closure for informational or stale items.
  • Offer backlog item creation for actionable issues via /kiln:kiln-report-issue to seed sustaining work in the .kiln/issues directory.

Quick Start

Process up to 50 open issues, filtering with --reanalyze to reprocess all; the system will output per-issue decisions and prompts for closures and backlog creation.

Frequently Asked Questions about kiln-analyze-issues

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

FAQPage Schema
How do I automate GitHub issue triage and labeling for my backlog?

Automate GitHub issue triage by categorizing open issues, applying category labels, and flagging actionable items with closure suggestions. The Skill processes up to 50 open issues per run, using an idempotent 'analyzed' label to track progress and avoid re-processing.

What categories does automated GitHub issue triage assign to issues?

GitHub issue triage assigns a primary category to each issue based on its content, including skills, agents, hooks, templates, scaffold, workflow, or other. These category labels are applied alongside an 'analyzed' label to track triage progress.

Do I need the gh CLI to categorize and label open GitHub issues?

Yes, the gh CLI must be installed and authenticated before triaging GitHub issues. The Skill reads issue fields like number, title, body, labels, createdAt, and updatedAt directly from GitHub using the authenticated CLI environment.

Can I reprocess all open GitHub issues after they have been triaged?

Yes, you can reprocess all triaged GitHub issues by running the Skill with the --reanalyze flag. This bypasses the idempotent 'analyzed' label filter and re-evaluates all open issues, returning updated per-issue decisions and closure recommendations.

How do I create backlog items from actionable GitHub issues?

For actionable GitHub issues, the Skill offers backlog item creation via /kiln:kiln-report-issue to seed sustaining work. This generates backlog options and saves them in the .kiln/issues directory for downstream development tracking.

What happens to stale or informational GitHub issues during triage?

During GitHub issue triage, stale or informational issues are flagged with closure recommendations. The Skill outputs per-issue decisions and prompts you to close these items, keeping the backlog focused on actionable work.