Verified:GitHub

issue-tracking

Manage deferred work in GitHub and GitLab issue trackers via gh and glab CLIs.

Updated Jun 6, 2026

Search Tags:#github #issue tracking #backlog #tech debt #gh cli #gitlab #triage

One-click install

npx skills add https://github.com/hacker-cb/claude-code-plugins --skill issue-tracking-hacker-cb

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: issue-tracking
Source: https://github.com/hacker-cb/claude-code-plugins/tree/main/plugins/hcb-dev/skills/issue-tracking
Command: npx skills add https://github.com/hacker-cb/claude-code-plugins --skill issue-tracking-hacker-cb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Deferred work — defects, tech debt, follow-ups found mid-task — gets lost when it lives only in chat or memory. This Skill keeps that work in the forge's issue tracker: it searches for existing coverage before opening duplicates, classifies and decomposes issues, rules whether old issues are still true of the code, and closes them correctly when work lands. ## Core Features & Use Cases - Duplicate-safe search and triage: Searches open and closed issues on GitHub (`gh issue list`) and GitLab (`glab issue list`) with pagination-cap handling, then decides between citing, updating, or opening an issue. - Closed-issue ruling table: Determines what a closed issue takes based on what closed it — a fix, a duplicate, a decision against, or nothing — including reopen and drop paths. - Issue currency checks: Answers questions like "is #42 still current?" with one of four verdicts and a proposed edit, plus correct closing-keyword and cross-reference citation handling per forge. - Use Case: While refactoring a module you spot a latent bug you won't fix now. The Skill searches the tracker, finds nothing covering it, drafts a properly structured issue with trigger, cost, and source, and files it only after your explicit go-ahead. ## Quick Start Ask the assistant to check whether the bug you just noticed is already tracked, and if not, file it as a new issue on the repository's forge.

Frequently Asked Questions about issue-tracking

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

FAQPage Schema

How do I file a GitHub or GitLab issue without creating a duplicate?▼

Search the tracker across all states before opening anything — on GitHub use gh issue list --state all --search, on GitLab use glab issue list -A with pagination. If a hit covers the finding, cite or update it; only open a new issue when nothing covers it.

How do I check if an old issue is still relevant to the current code?▼

Rule the issue against the refreshed codebase using the issue-currency reference, which yields one of four verdicts. A verdict past current is proposed with its edit — body rewrite, closure, or reclassification — and applied only after user approval.

Does this work with both GitHub and GitLab repositories?▼

Yes, it supports GitHub via the gh CLI and GitLab via the glab CLI. The forge is detected from what the git remote answers, never from the hostname, and each forge's closing keywords and pagination behavior are handled separately.

When should a finding become an issue versus being fixed immediately?▼

Only consciously deferred work earns an issue — a defect, follow-up, or tech debt left for later. Work conceived and finished in the same effort earns none, since the change request and git log already record it.

Can the assistant close or reopen issues on its own?▼

No. Every write to the tracker — opening, updating, closing, reopening — waits for an explicit user answer or a delegation named in a session order. A standing instruction to work autonomously authorizes the work, not tracker writes.