skills.rest
glhewett
glhewettCOMMUNITY
Explore all skills by this author →
Website𝕏@greg_hewettGitHub

issues-close

Close TOML issues by updating metadata, appending comments, and committing.

Updated Feb 15, 2026
Search Tags:#automation#git#commit#cli#toml#issue-tracking#issue-management
One-click install
npx skills add https://github.com/glhewett/public-skills --skill issues-close
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issues-close
Source: https://github.com/glhewett/public-skills/tree/main/issues-close
Command: npx skills add https://github.com/glhewett/public-skills --skill issues-close

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the final step of issue workflows by reliably marking an issue as closed in the repository, updating its metadata, logging a closure comment, and committing the change so the closure is recorded and pushed to the remote.

Core Features & Use Cases

  • Safe file validation: Verifies the presence of the .issues/{id}.toml file before making changes.
  • TOML metadata updates: Sets status to closed, marks closed=true, and appends a comments entry with author, date, and reason.
  • Git integration: Captures the git user email, stages the updated issue file, commits with a structured message, and pushes to remote.
  • Use Case: When finishing work on an issue, use this Skill to close the issue file, add a closure comment for auditability, and push the commit to the repository.

Quick Start

Close issue 0001 by invoking the issues-close skill with the issue ID and providing a clear reason for why it is being closed.

Frequently Asked Questions about issues-close

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

FAQPage Schema
How do I close a TOML issue file and commit the change?▼

To close a TOML issue, the skill updates the file's status and closed fields, appends a closure comment with the author and date, then stages and commits the change to git before pushing to remote.

How does issue tracking work with a .issues directory?▼

Issue tracking with a .issues directory uses numbered TOML files to store issue metadata and comments. The skill reads these files, updates their status to closed, and logs a closure reason directly in the file.

Can I automate issue closure and push the commit to my remote repository?▼

Yes, you can automate issue closure by invoking the skill with an issue ID and reason. It stages the updated TOML file, commits with a structured message, and pushes the commit to your configured remote repository.

Does this issue management workflow require a specific file format?▼

Yes, this issue management workflow requires numbered TOML issue files inside a .issues directory. The skill validates the existence of the specific issue file before applying any metadata updates or closure comments.

What is the best way to document a closure reason for an issue in git?▼

The best way to document a closure reason is to append a comments entry to the issue's TOML file. The skill captures your git user email, adds the reason with a date, and commits the file for auditability.

What happens if the issue file does not exist in the .issues directory?▼

If the issue file does not exist, the skill performs an existence check and will not make changes. It validates the presence of the .issues/{id}.toml file before attempting to read or update TOML fields.

Related Skills

Explore More Software Engineering Skills→
glhewettglhewett

issues-complete

Close TOML issue files by updating status, appending comments, and committing changes.

Community
Intermediate
NimbalystNimbalyst
25

commit-helper

Generate impact-focused Git commit messages from code changes and history.

Official
Basic
glhewettglhewett

issues-create

Create TOML issue files with computed IDs and stage them with git.

Community
Intermediate
glhewettglhewett

issues-comment

Append a chronological comment to an issue stored in .issues/*.toml.

Community
Intermediate