issues-list

List open issues from .issues/*.toml files as a markdown table.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/glhewett/public-skills --skill issues-list
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issues-list
Source: https://github.com/glhewett/public-skills/tree/main/issues-list
Command: npx skills add https://github.com/glhewett/public-skills --skill issues-list

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly discovers and summarizes open issues stored in a repository's .issues directory so maintainers can get an at-a-glance view without manually opening files.

Core Features & Use Cases

  • Finds .issues/*.toml files using globbing and reads each file to collect issue metadata.
  • Parses TOML fields (id, title, status, priority, assigned_to, closed), filters out closed issues, sorts by ID, and renders a markdown table.
  • Use case: obtain a clean list of active tasks before starting a sprint or preparing a changelog.

Quick Start

List all open issues and display them in a markdown table sorted by ID.

Frequently Asked Questions about issues-list

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

FAQPage Schema
How do I list open issues from TOML files in a git repository?

List open issues from TOML files by reading and parsing .issues/*.toml configurations, filtering out closed statuses, and sorting active entries by ID to render a concise markdown table.

What is the best way to view git-based issue tracking metadata as a table?

View git-based issue tracking metadata by parsing TOML issue files to extract id, title, status, and priority fields, then formatting the filtered open issues into a structured markdown table.

Can I use this to filter closed issues and sort active tasks by ID?

Filter closed issues and sort active tasks by ID by evaluating the status field in TOML files, excluding resolved items, and ordering remaining open issues numerically before table rendering.

Does this issue tracking approach work for solo contributors using git-based workflows?

Designed for solo contributors using git-based workflows, this approach stores issues as lightweight .issues/*.toml files, avoiding external platforms while maintaining a local task list.

How do I prepare a changelog or sprint view from TOML issue files?

Prepare a changelog or sprint view from TOML issue files by aggregating open issue metadata into a markdown table, providing an at-a-glance summary of active tasks before development.