mk.issues

Automates GitHub issue triage, deep-dive and bulk review with gh CLI, outputting structured reports without modifying the repository.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mayknxyz/my-kit --skill mk-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mk.issues
Source: https://github.com/mayknxyz/my-kit/tree/main/kit/.claude/skills/mk.issues
Command: npx skills add https://github.com/mayknxyz/my-kit --skill mk-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Triage, deep-dive, and bulk-review GitHub issues to surface actionable insights and keep backlogs healthy.

Core Features & Use Cases

  • Triage: assess completeness, clarity, and staleness; suggest canonical labels; flag potential duplicates; produce an issue triage report.
  • Deep-dive: analyze a single issue, fetch details, scan codebase for related files, assess validity and complexity, and propose an implementation plan.
  • Bulk review: analyze all open issues, categorize by type, detect duplicates, compute health metrics, and generate a bulk health report for backlog prioritization.

Quick Start

Run /mk.review.issues triage in your repository to generate a preliminary triage report.

Frequently Asked Questions about mk.issues

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

FAQPage Schema
How do I automate GitHub issue triage for repositories with multiple contributors?

Automating GitHub issue triage uses the gh CLI to fetch open issues, assess staleness and clarity, flag duplicates, suggest canonical labels, and output a structured triage report without modifying repository state.

What is the best way to bulk review GitHub issues for backlog prioritization?

Bulk reviewing GitHub issues involves analyzing all open entries, categorizing by type, detecting duplicates, computing health metrics, and generating a comprehensive report to drive actionable backlog prioritization.

Can I analyze a single GitHub issue and propose an implementation plan?

Deep-diving a single GitHub issue fetches details, scans the codebase for related files, assesses validity and complexity, and proposes an implementation plan to surface actionable insights.

Does the GitHub issue review process modify my repository state?

The GitHub issue review process does not modify repository state; it leverages gh CLI to fetch data and loads canonical labels strictly to output structured, read-only triage and health reports.

How do I identify duplicate GitHub issues across an active tracker?

Identifying duplicate GitHub issues during bulk review analyzes all open entries, detects overlapping contexts, and flags potential duplicates to keep backlogs healthy without altering repository data.

When do I need to triage GitHub issues with canonical labels?

Triage GitHub issues with canonical labels when repositories have active trackers and multiple contributors, needing to assess completeness, suggest labels, and surface actionable prioritization safely.