close

Clean up GitHub issue claims and session metadata after coding tasks.

2|Updated Feb 23, 2026

Search Tags:#automation #workflow #github #session management #cleanup #issue tracking

Ready to run

npx skills add https://github.com/evanharmon1/harmon-devkit --skill close-evanharmon1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: close
Source: https://github.com/evanharmon1/harmon-devkit/tree/main/ai/skills/universal/close
Command: npx skills add https://github.com/evanharmon1/harmon-devkit --skill close-evanharmon1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents the accumulation of stale GitHub issues, abandoned claims, and unorganized session history by enforcing a rigorous end-of-session ritual.

Core Features & Use Cases

Claim Lifecycle Management: Automatically detects and releases stale issue claims, labels, and assignments to ensure board accuracy.
Session Housekeeping: Validates uncommitted work and provides a standardized command to rename sessions for better discoverability.
Use Case: After finishing a coding task, use this skill to ensure your GitHub project board is updated, your PRs are referenced correctly, and your session is archived with a clear, searchable name.

Quick Start

Invoke the close skill to audit your current session and generate the final rename command for your session history.

Frequently Asked Questions about close

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

FAQPage Schema

How do I automate cleanup of stale GitHub issue claims and assignments?▼

To automate cleanup of stale GitHub issue claims, you need a rigorous end-of-session ritual that detects abandoned assignments and releases labels. This enforces atomic marker removal to maintain project board integrity and syncs local session state with remote issue tracking.

What is the best way to standardize session naming conventions for GitHub workflow history?▼

Standardizing session naming conventions involves auditing your current session and generating a final rename command. This enforces consistent session naming for better discoverability, ensuring your archived coding sessions remain searchable and properly organized within your workflow history.

How does session metadata synchronization work with GitHub project boards?▼

Session metadata synchronization works by automatically detecting and releasing stale issue claims, labels, and assignments to ensure board accuracy. It applies atomic marker removal to maintain consistent synchronization between local session state and remote GitHub issue tracking.

When do I need to run session housekeeping for uncommitted work and issue tracking?▼

You need to run session housekeeping after finishing a coding task to validate uncommitted work and update your GitHub project board. This end-of-session ritual prevents the accumulation of stale issues, abandoned claims, and unorganized session history.

Does GitHub issue cleanup require atomic marker removal for project board integrity?▼

Yes, GitHub issue cleanup requires atomic marker removal to satisfy requirements for consistent session naming conventions and project board integrity. This ensures stale claims and assignments are fully released without leaving orphaned metadata in the issue tracking system.

Why does stale issue tracking accumulate in GitHub project boards during software development?▼

Stale issue tracking accumulates when development workflows lack a rigorous end-of-session ritual to synchronize local session state with remote issue tracking. Without automated claim lifecycle management, abandoned assignments and uncommitted work remain on the project board, reducing accuracy.