My Issues

A personal issue tracking skill that helps developers view, filter, and manage their assigned GitHub issues across all repositories from a single command-line interface.

What Is This?

Overview

This skill provides a unified view of all GitHub issues assigned to you across multiple repositories. It covers filtering by state, labels, priority, and repository, along with quick status updates and batch operations for efficient personal issue management.

Who Should Use This

Perfect for developers juggling issues across multiple repositories, open source contributors tracking their commitments, team leads monitoring their assigned work, and anyone who needs a consolidated view of their GitHub issue workload.

Why Use It?

Problems It Solves

Developers often work across 5 to 10 repositories simultaneously. Checking each repo's issue tracker individually wastes time and causes tasks to slip through cracks. This skill aggregates all your issues into a single, filterable view with quick action capabilities.

Core Highlights

• Cross-Repo View - See all assigned issues from every repository in one list
• Smart Filtering - Filter by state, labels, priority, repo, or date range
• Quick Actions - Comment, close, or reassign issues without leaving terminal
• Priority Sorting - Sort by urgency, staleness, or recent activity
• Status Dashboard - Overview of open, in-progress, and blocked issue counts

How to Use It?

Basic Usage

Ask Claude about your issues, and this skill queries GitHub for your assignments.

Scenario 1: Viewing All Assigned Issues

Ask Claude: "Show me all my open issues"

Claude will query and display:

gh issue list --assignee @me --state open

gh search issues --assignee=@me --state=open --owner=myorg

gh search issues --assignee=@me --state=open --json repository,title,labels,updatedAt --jq '.[] | "\(.repository.name)#\(.number): \(.title)"'

gh search issues --assignee=@me --label="bug" --state=open

gh search issues --assignee=@me --state=open --sort=updated --order=desc

Scenario 2: Quick Issue Triage

Tell Claude: "Show my stale issues that need attention"

Claude will find issues with no recent activity:

gh search issues --assignee=@me --state=open --updated="<$(date -d '14 days ago' +%Y-%m-%d)"

gh search issues --assignee=@me --state=open --comments=0

gh issue close 42 --repo owner/project --comment "Fixed in PR #58"

Real-World Examples

Sprint Review Preparation

A developer used this skill to pull all issues closed during the sprint across 4 repositories. The consolidated list formed the basis of their sprint review demo, saving 30 minutes of manual tracking.

Open Source Contribution Tracking

An open source contributor tracked assigned issues across 12 community projects. Filtering by staleness helped prioritize which contributions needed immediate attention.

Advanced Tips

Custom Issue Dashboard

Combine search queries with jq formatting to create a personalized terminal dashboard showing issue counts by repository, priority distribution, and aging metrics.

Automated Reminders

Script periodic issue checks that highlight stale assigned issues. Run daily via cron to surface forgotten tasks before they become overdue.

When to Use It?

Use Cases

• Daily Standup Prep - Review assigned issues before team standups
• Sprint Planning - Assess current workload across repositories
• Issue Triage - Identify and prioritize stale or blocked issues
• Progress Reporting - Generate lists of completed issues for status updates
• Workload Balance - Visualize issue distribution across projects

Related Topics

When you ask Claude these questions, this skill will activate:

• "Show me my open issues"
• "What issues are assigned to me?"
• "Find my stale issues across repos"
• "List my bugs and feature requests"

Important Notes

Requirements

• GitHub CLI (gh) version 2.0+ installed and authenticated
• GitHub account with repository access for assigned issues
• Organization membership for org-wide issue searches
• API rate limits apply for large cross-repo queries

Usage Recommendations

Do:

• Check issues daily - Stay on top of assignments across all repos
• Use labels consistently - Enable effective filtering by priority and type
• Close resolved issues promptly - Keep your issue list accurate
• Add context when commenting - Help future you understand decisions

Don't:

• Don't ignore stale issues - Reassign or close issues you cannot address
• Don't hoard assignments - Unassign yourself from deprioritized work
• Don't skip label filters - Unfiltered lists become overwhelming quickly

Limitations

• Cross-organization searches require separate authentication
• GitHub API rate limits may throttle large queries
• Private repo issues only visible with appropriate access tokens
• Real-time notifications require separate webhook configuration