skills.rest
hpark0011
hpark0011COMMUNITY
Explore all skills by this author →
GitHub

triage-issue-tickets

Reviews ticket files and cancels or completes outdated ones based on codebase state.

Updated Apr 17, 2026
Search Tags:#markdown#cleanup#issue tracking#backlog#tickets#triage#frontmatter
One-click install
npx skills add https://github.com/hpark0011/mirror --skill triage-issue-tickets-hpark0011
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage-issue-tickets
Source: https://github.com/hpark0011/mirror/tree/main/.agents/skills/triage-issue-tickets
Command: npx skills add https://github.com/hpark0011/mirror --skill triage-issue-tickets-hpark0011

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Backlogs accumulate stale tickets that are no longer relevant or have already been resolved, making it hard to see what work actually remains. This Skill cleans up the to-do ticket queue by verifying each ticket against the current codebase. ## Core Features & Use Cases - Cancel irrelevant tickets: Marks tickets as canceled and moves them to workspace/tickets/canceled/ when their premise no longer holds, they are superseded, or they are duplicates. - Complete already-solved tickets: Verifies whether the work was actually done by reading the affected files (not just git log), then marks them completed and moves them to workspace/tickets/completed/. - Use Case: After a large refactoring sprint, run a triage pass over workspace/tickets/to-do/ to cancel obsolete tickets and close ones the refactor already addressed, leaving only genuinely open work. ## Quick Start Triage the tickets in my to-do backlog and cancel or complete the ones that no longer apply.

Frequently Asked Questions about triage-issue-tickets

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

FAQPage Schema
How do I clean up a stale ticket backlog?▼

Review each ticket in the to-do directory against the current codebase state. Cancel tickets whose premise no longer holds or that are duplicates, and mark tickets completed when the work is verifiably done, moving each file to the appropriate status directory.

How to verify a ticket is already resolved before closing it?▼

Read the actual files the ticket affects and confirm the described change or fix exists in the code. Do not rely on git log alone, since commit messages can be misleading or the work may have been reverted.

Does triaging tickets also resolve open issues?▼

No, triage only reclassifies tickets as canceled or completed based on existing codebase state. Tickets that still represent genuine open work stay in the to-do directory and require a separate resolution workflow.

When should a ticket be canceled instead of completed?▼

Cancel a ticket when its premise no longer holds, it has been superseded by other work, or it duplicates another ticket. Mark it completed only when the requested work has verifiably been done in the codebase.

Related Skills

Explore More Software Engineering Skills→
tmart2322tmart2322

submit-idea

Captures stray product and feature ideas into centralized docs/ideas inbox as markdown files.

Community
Intermediate
atrislabsatrislabs

autopilot

Execute iterative Plan-Do-Review loops for feature development and bug fixing.

Official
Advanced
propane-aipropane-ai
4

design-priorities

Prioritize design backlogs using impact-effort scoring and roadmap alignment.

Official
Intermediate
phoenixvcphoenixvc

sync-backlog

Synchronize local backlog items with GitHub or Linear issue trackers.

Official
Advanced