name: tg-issues
description: List open issues from the current project's GitHub repo. Use to see your backlog, find issues to work on, or check issue status. Triggers include "/tg-issues", "show my issues", "what issues do we have", "list backlog".

Issue Tracker - List GitHub Issues

Overview

View open issues for the current project's GitHub repo. Designed for Tejas's workflow: quickly see what's logged, pick something to tackle.

When to Use

Use this skill when:
- You want to see what issues are logged
- You're ready to tackle some backlog items
- You want to check if something was already logged
- You need to prioritize what to work on

The Workflow

Step 1: Detect GitHub Repo

# Get the GitHub repo from git remote
git remote get-url origin 2>/dev/null

If no GitHub repo found:

This project doesn't have a GitHub remote configured. No issues to show.

Step 2: Fetch Issues

# Get repo in owner/repo format
REPO=$(git remote get-url origin | sed 's/.*github.com[:/]\(.*\)\.git/\1/' | sed 's/.*github.com[:/]\(.*\)/\1/')

# List open issues
gh issue list --repo "$REPO" --state open --limit 20

Step 3: Display Issues

Format the output clearly:

## Open Issues - [repo-name]

| # | Title | Labels | Created |
|---|-------|--------|---------|
| [#12](url) | Fix search filter | `bug` `P2-high` | 2 days ago |
| [#11](url) | Add dark mode | `enhancement` `P3-medium` | 5 days ago |
| [#8](url) | Improve loading speed | `task` `P4-low` | 1 week ago |

**Total**: 3 open issues

---

**Quick actions:**
- View details: `gh issue view 12`
- Start working: "Let's tackle issue #12"
- Close an issue: `gh issue close 12`

If no issues:

## Open Issues - [repo-name]

No open issues! Your backlog is clear.

To log a new issue, use `/tg-issue`.

Step 4: Optional Filtering

If the user asks for filtered results:

By priority:

gh issue list --repo "$REPO" --state open --label "P1-critical"

By type:

gh issue list --repo "$REPO" --state open --label "bug"

By search term:

gh issue list --repo "$REPO" --state open --search "dark mode"

Show closed issues:

gh issue list --repo "$REPO" --state closed --limit 10

Display Variants

Default View (Compact Table)

Best for quick overview:

## Open Issues - flight-tracker (3 open)

| # | Title | Labels | Age |
|---|-------|--------|-----|
| #12 | Search filter fails with multiple categories | `bug` `P2-high` | 2d |
| #11 | Add dark mode support | `enhancement` `P3-medium` | 5d |
| #8 | Optimize chart rendering | `task` `P4-low` | 1w |

→ View details: "tell me about issue #12"
→ Work on one: "let's fix issue #12"

Detailed View (When Asked)

If user says "show me details" or asks about a specific issue:

gh issue view 12 --repo "$REPO"

## Issue #12: Search filter fails with multiple categories

**Status**: Open
**Labels**: `bug`, `P2-high`
**Created**: 2 days ago
**URL**: https://github.com/tejasgadhia/flight-tracker/issues/12

### Description

Search filter doesn't work correctly when multiple categories are selected.

**Steps to Reproduce:**
1. Open search
2. Select multiple categories
3. Observe incorrect/no results

**Expected**: Results filtered by all selected categories
**Actual**: Filter fails or returns incorrect results

---

**Actions:**
- "Let's fix this" - Start working on the issue
- "Close this" - Mark as resolved
- "Change priority to P1" - Update labels

Priority View

If user asks "what's urgent?" or "show by priority":

## Issues by Priority - flight-tracker

### P1-Critical (0)
No critical issues.

### P2-High (1)
- #12: Search filter fails with multiple categories (`bug`)

### P3-Medium (1)
- #11: Add dark mode support (`enhancement`)

### P4-Low (1)
- #8: Optimize chart rendering (`task`)

---

**Recommendation**: Start with #12 (highest priority bug)

Interaction Patterns

User wants to work on an issue:

User: "let's tackle issue #12"

→ Fetch full issue details with `gh issue view 12`
→ Present the problem clearly
→ Start working on the solution

User wants to close an issue:

User: "close issue #12, we fixed it"

→ Run `gh issue close 12 --repo "$REPO"`
→ Confirm: "Issue #12 closed!"

User wants to update an issue:

User: "change #12 to P1-critical"

→ Run `gh issue edit 12 --add-label "P1-critical" --remove-label "P2-high" --repo "$REPO"`
→ Confirm: "Updated #12 to P1-critical"

Error Handling

No git repo:

This directory isn't a git repository. Navigate to a project directory first.

No GitHub remote:

This project doesn't have a GitHub remote. No issues to show.

gh CLI not authenticated:

GitHub CLI isn't authenticated. Run:
gh auth login

API rate limit:

GitHub API rate limit reached. Try again in a few minutes, or view issues directly:
https://github.com/tejasgadhia/[repo]/issues

Success Criteria

• Issues displayed clearly with relevant info
• Easy to scan and prioritize
• Quick actions available for common tasks
• Graceful handling when no issues exist