issues-complete
Complete an issue by marking it as closed with a closing comment.
Arguments
The argument is the issue ID, e.g. 0001 or 1. If the ID is not zero-padded, pad it to 4 digits (e.g. 1 becomes 0001).
Steps
- •Parse the argument as an issue ID. Zero-pad it to 4 digits.
- •Use the Glob tool to verify
.issues/{id}.tomlexists. - •If the file does not exist, inform the user and stop.
- •Read the issue file using the Read tool and display all its fields to the user.
- •Ask the user for a closing comment explaining why/how the issue was resolved.
- •Update the issue file:
- •Set
status = "complete" - •Set
closed = true
- •Set
- •Run
git config user.emailusing the Bash tool to get the current user's email. - •Append a
[[comments]]entry to the end of the issue file using the Edit tool to log the completion. Use the current date inYYYY-MM-DDformat. Format:
toml
[[comments]]
author = "{email}"
date = "{today}"
message = "Issue completed: {closing comment}"
- •Run
git add .issues/{id}.tomlusing the Bash tool. - •Confirm to the user that the issue has been completed.
- •Invoke
/git-commitusing the Skill tool to commit the changes. - •Invoke
/git-feature-completeusing the Skill tool to merge to the main branch.
Allowed tools
- •
Bash(git *)- for git add - •
Read- for reading the issue file - •
Write- for writing the updated issue file - •
Glob- for verifying the issue file exists - •
Skill(git-commit)- for committing the changes