GitHub Issue Analyzer & Triager FAQs

Question 1

How does this skill determine if a GitHub issue is already fixed?

Accepted Answer

The skill performs keyword extraction from the issue description and then searches git logs, PR history, and the current codebase for specific patterns or commit messages that indicate a resolution.

Question 2

Can this skill automatically close issues on GitHub?

Accepted Answer

Yes, it provides predefined classification actions and templates that use the GitHub CLI to close issues with detailed comments citing PRs, commits, or architectural changes as evidence.

Question 3

How does the skill handle old or stale issues?

Accepted Answer

It uses age-based heuristics to evaluate relevance. Issues older than 6-12 months are scrutinized for architectural relevance and are often classified as 'Outdated' if the feature has been refactored.

Question 4

What information does the skill collect from an issue?

Accepted Answer

It fetches the title, body, labels, comments, creation date, and last activity date using the GitHub CLI to build a complete profile for analysis.

Question 5

Does it support migrating issues to other tools like Linear?

Accepted Answer

Yes, it includes a specific phase for creating structured Linear tickets from GitHub issues, ensuring all technical notes, reproduction steps, and original context are preserved.

GitHub Issue Analyzer & Triager

Key Features

Use Cases

GitHub Issue Analyzer & Triager

Key Features

Use Cases