Display formatted details from .issues/{id}.toml issue files.
npx skills add https://github.com/glhewett/public-skills --skill issues-show
Please help me install this Agent Skill. Skill: issues-show Source: https://github.com/glhewett/public-skills/tree/main/issues-show Command: npx skills add https://github.com/glhewett/public-skills --skill issues-show
Quickly locating and reading the full contents of an issue stored in the repository as a .toml file can be tedious and error-prone when IDs are inconsistently formatted or comments are buried. This Skill standardizes lookup, validation, and human-friendly presentation so maintainers and contributors can review an issue's status, metadata, and discussion without manually opening files.
Ask the issues-show skill to display issue 1 by providing the issue ID 1 and receive a formatted summary including comments.
High-intent search queries and answers about installing and using this skill.
To read issue details from a local TOML file, this skill validates the issue ID, zero-pads it to four digits, checks for the .issues/{id}.toml file, and formats the contents for review.
Looking up inconsistently formatted issue IDs is handled by normalizing numeric inputs through zero-padding to four digits, ensuring the correct .issues/{id}.toml file is found and displayed.
Yes, you can view issue comments and metadata without opening TOML files manually because this skill parses the file and renders the title, status, priority, assignee, timestamps, and comments in a readable format.
The best way to triage local repository issues stored as TOML is to use an automated lookup tool that validates IDs and formats the full file contents, allowing maintainers to quickly review status and discussion history.
Yes, this issue tracking display method works without external dependencies, relying only on glob-based existence checking to verify and read the .issues/{id}.toml file directly from the repository.
Your issue lookup may fail because the skill requires numeric IDs to be zero-padded to four digits for file lookup, meaning an input like 1 must resolve to 0001 to find the correct TOML file.
glhewettCreate TOML issue files with computed IDs and stage them with git.
glhewettCreate implementation plans from issue titles and comments in .issues/*.toml files.
mulhamnaUpdate assignee or priority for Jira issues matched by a JQL query.
ederfmatosGenerate review round directories and issue files from PRD implementations.