issues-complete

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the repetitive and error-prone process of manually editing repository issue files, updating their status, and performing the associated git operations required to record and merge the change.

Core Features & Use Cases

  • Automated Closure: Validates the issue file exists, zero-pads the issue ID, sets status and closed flags, and appends a timestamped closing comment authored with the current git user email.
  • Git Workflow Integration: Stages and commits the updated issue file and then completes the feature branch by invoking the repository's feature-complete skill.
  • Use Case: When finishing work on an issue stored as .issues/0003.toml, use this Skill to record the resolution, commit the update, and merge the branch without manual file edits.

Quick Start

Invoke the issues-complete skill with the issue ID 3 to add a closing comment, commit the updated .issues/0003.toml, and complete the feature branch.

Frequently Asked Questions about issues-complete

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

FAQPage Schema
How do I close a git issue stored as a TOML file and merge the branch?

To close a git issue stored as a TOML file, this skill updates the issue status, appends a timestamped closing comment, stages the file via git-commit, and merges the feature branch.

What is the best way to automate appending closing comments to issue tracking files?

Automating closing comments for issue tracking files involves reading the TOML issue file, appending a comment with the current git user email and date, and committing the change to git.

Does this issue closure workflow require a specific file structure?

Yes, this workflow requires repositories that store issues as .issues/*.toml files and utilize feature branch workflows to successfully commit changes and merge branches.

How do I zero-pad an issue ID when updating issue tracking files in git?

When updating issue tracking files in git, the skill automatically zero-pads the issue ID to format the filename correctly before reading and editing the TOML issue file.

Can I use this skill to record issue resolution without manual file edits?

Yes, you can record issue resolution without manual file edits by invoking the skill with an issue ID to automatically set closed flags, append comments, and complete the feature branch.