issue-close

Name: issue-close
Availability: InStock
Author: mikersays

Automates ticket closure in documentation repositories with verification tracking and INDEX.md updates.

Updated Feb 22, 2026

Search Tags:#git #verification #document update #ticket tracking #issue closure

Ready to run

npx skills add https://github.com/mikersays/mikersays-plugins --skill issue-close-mikersays

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issue-close
Source: https://github.com/mikersays/mikersays-plugins/tree/main/plugins/issues/skills/issue-close
Command: npx skills add https://github.com/mikersays/mikersays-plugins --skill issue-close-mikersays

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of closing tickets, ensuring that documentation accurately reflects the status of issues and maintaining a detailed history for future reference.

Core Features & Use Cases

Ticket Closure: Automates marking tickets as fixed post-merge, ensuring accurate status updates.
Verification Tracking: Captures and stores verification details based on actual testing, maintaining the integrity of the issue history.
Documentation Updates: Updates the ticket status in INDEX.md and appends to the 'Done' section for easy reference.
Paired Ticket Handling: Handles paired tickets with individual verifications but shared commit SHA for consistency.
Use Case: Perfect for teams that rely on detailed issue tracking and want to minimize the risk of undetected bugs by ensuring thorough verification before closing tickets.

Quick Start

Use the issue-close skill to mark a ticket as fixed by saying "close ticket NNNN" or "mark NNNN fixed".

Frequently Asked Questions about issue-close

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

FAQPage Schema

How do I automate issue closure and update documentation after a git merge?▼

To automate issue closure, the skill updates ticket statuses to fixed, captures testing verification details, and appends entries to the 'Done' section in INDEX.md after a git branch merge.

What is the best way to track verification details for closed tickets in a markdown repository?▼

Tracking verification details for closed tickets involves capturing actual testing outcomes and updating the INDEX.md document, ensuring the issue history accurately reflects the verification status for future reference.

Does this issue closure process handle paired tickets with shared commit SHAs?▼

Yes, the issue closure process handles paired tickets by recording individual verification details for each ticket while linking them to a shared commit SHA for consistent git tracking.

Do I need git commands to mark tickets as fixed and update the INDEX document?▼

Yes, you need git commands for branch checking and merging, alongside markdown processing, to successfully update the INDEX document and mark tickets as fixed.

Can I use this skill for teams that require thorough issue tracking before closing tickets?▼

Yes, you can use this skill for teams requiring thorough issue tracking, as it minimizes undetected bugs by enforcing detailed verification capture before finalizing ticket closure.