issue-list-report

Generate formatted local Markdown reports from issue tracker query results.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/astroville/sprout --skill issue-list-report-astroville
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-list-report
Source: https://github.com/astroville/sprout/tree/main/.claude/skills/issue-list-report
Command: npx skills add https://github.com/astroville/sprout --skill issue-list-report-astroville

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a local, readable summary of issues from an issue tracker is tedious: issues get closed, reassigned, or fixed, and manually maintaining a report leads to stale, noisy documents. This Skill produces and maintains a consistently formatted Markdown issue list report. ## Core Features & Use Cases - Structured Report Generation: Creates a Markdown report with highlights (totals, new issues, severity counts) and a per-issue list including severity, reporter, age, and a concise summary. - Report Maintenance: Removes issues that are no longer open or have been reassigned, and tags or strikes through issues whose fixes have been submitted as PRs. - Use Case: After querying your issue tracker for open bugs assigned to you, generate a scannable local report, then update it as issues are closed or PRs are submitted. ## Quick Start Generate an issue list report from the issues I just queried and format it with highlights and per-issue summaries.

Frequently Asked Questions about issue-list-report

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

FAQPage Schema
How do I create a local report from issue tracker results?▼

Query your issue tracking system for the desired issues, then use this Skill to generate a Markdown report. It produces a highlights section with totals and severity counts plus a formatted per-issue list with severity, reporter, creation date, and age.

How do I keep an issue list report up to date?▼

Re-run the Skill after querying the tracker again. It removes issues that are no longer open or have been assigned to others, and tags or strikes through issues whose fixes have been submitted as PRs.

What format does the issue list report use?▼

The report is Markdown with a header showing generation time, total count, and filter description, a Highlights section with totals and severity counts, and an Issue List section with one entry per issue including severity, reporter, age, and a short summary.

When should I not use an issue list report?▼

Avoid it when you need real-time tracker synchronization or team-wide dashboards, since the report is a local static snapshot. It is best suited for personal tracking and point-in-time summaries rather than replacing the issue tracker itself.