Remove closed .toml issue files and commit the purge.
npx skills add https://github.com/glhewett/public-skills --skill issues-purge
Please help me install this Agent Skill. Skill: issues-purge Source: https://github.com/glhewett/public-skills/tree/main/issues-purge Command: npx skills add https://github.com/glhewett/public-skills --skill issues-purge
Removes stale closed issues that remain as .toml files in the repository, preventing clutter and keeping the issue tracker and git history consistent.
Run the issues-purge skill to locate closed .toml issue files, confirm deletion, and commit their removal from the repository.
High-intent search queries and answers about installing and using this skill.
To batch delete closed issues stored as TOML files, the skill glob-scans .issues/*.toml, parses for closed = true, runs git rm on matches, and commits a single purge message to keep git history consistent.
The best way to clean up stale issue files without losing tracking is running git rm on closed TOML files and consolidating removals into a single purge commit, preserving repository consistency and traceability.
Yes, you can automatically find and remove closed issues in a file-based tracker by globbing .issues/*.toml, parsing TOML to detect closed = true, and executing git rm for confirmed deletions.
Yes, the issue purge workflow requires manual confirmation; it surfaces parsed issue IDs and titles for review before executing git rm and committing the consolidated removal message.
Purging closed TOML issues is designed for small projects or solo contributor workflows using file-based issue tracking, ensuring safe removal and git commits without overhead for large teams.
glhewettList open issues from .issues/*.toml files as a markdown table.
dyoshikawaIdentify and delete stale local and remote-tracking git branches.
ImperialAutomationAutomate git branch cleanup by deleting merged feature branches.
changoo89Delete git-tracked files with git rm and move untracked files to .trash.
