issue-check

Scan Markdown issue files and summarize open issues by priority.

1|Updated Jan 29, 2015
One-click install
npx skills add https://github.com/hayamiz/catscope --skill issue-check-hayamiz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-check
Source: https://github.com/hayamiz/catscope/tree/main/.claude/skills/issue-check
Command: npx skills add https://github.com/hayamiz/catscope --skill issue-check-hayamiz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collects and surfaces all currently open issues stored in doc/issues, enabling rapid triage and reporting.

Core Features & Use Cases

  • Scan doc/issues for Markdown issue files, excluding CLAUDE.md and the resolved/ subdirectory.
  • Read YAML frontmatter from each file to extract status, priority, and creation info.
  • Filter to issues with status: open, in-progress, or blocked; sort by priority (critical > high > medium > low) and then by issue number; present as a table plus a concise summary.

Quick Start

Run the issue-check skill to generate a live report of open issues from doc/issues.

Frequently Asked Questions about issue-check

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

FAQPage Schema
How do I summarize open issues from Markdown files with YAML frontmatter?

To summarize open issues, scan your doc/issues directory to read YAML frontmatter from Markdown files, filtering for open, in-progress, or blocked statuses and sorting by priority and issue number to present a triage table.

How do I triage project issues by priority using frontmatter metadata?

Triage project issues by reading YAML frontmatter to extract priority levels, then sort issues from critical to low alongside issue numbers, outputting a structured table with total counts and status breakdowns for rapid review.

Does issue tracking with Markdown frontmatter support excluding resolved files?

Yes, issue tracking with Markdown frontmatter supports excluding resolved files by ignoring the resolved/ subdirectory and specific files like CLAUDE.md, ensuring only currently open issues are surfaced in the final summary.

What is the best way to track open issues stored as Markdown files in a repository?

The best way to track open issues stored as Markdown files is to parse their YAML frontmatter for status and priority, filter out resolved entries, and generate a live report sorted by priority for immediate triage.

Can I generate a status breakdown report for in-progress and blocked issues?

Yes, you can generate a status breakdown report by scanning issue files for statuses like in-progress and blocked, aggregating total counts, and presenting a summary table sorted by priority and issue number.

Why does my issue scan include resolved files when they should be excluded?

Your issue scan might include resolved files if the tool is not configured to ignore the resolved/ subdirectory and CLAUDE.md file, which are explicitly excluded during the frontmatter parsing process to surface only open issues.