My Issues
Surface GitHub issues assigned to you in the current repo and rank what to tackle next by age, discussion, and status.
Overview
My Issues is an agent skill for the Build phase that lists your assigned GitHub issues in the current repo and suggests what to focus on next.
Install
npx skills add https://github.com/github/awesome-copilot --skill my-issuesWhat is this skill?
- Searches the active repository context for issues assigned to you
- Uses GitHub repo metadata and list_issues style workflows
- Suggests focus candidates using issue age and comment volume
- Factors open versus closed status into recommendations
- Keeps output actionable for daily solo-builder standups
- 3 prioritization signals: issue age, comment count, open/closed status
Adoption & trust: 9.6k installs on skills.sh; 34.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You lose time scanning GitHub manually to see which assigned issues are stale, noisy, or still blocking progress.
Who is it for?
Solo maintainers and indie devs using GitHub Issues in the repo they already have open in the agent.
Skip if: Multi-repo program management, Jira-only teams, or workflows without GitHub issue assignment.
When should I use this skill?
You are in a GitHub repo and want assigned issues listed with suggested focus order.
What do I get? / Deliverables
You receive a concise assigned-issue list with heuristic priorities so you can pick the next fix or PR without tab switching.
- Assigned issue inventory for the active repo
- Ranked suggestions for what to work on next
Recommended Skills
Journey fit
Issue triage sits in Build when you are actively executing against the repo backlog, not during initial idea research. PM subphase fits because the skill prioritizes assigned work items rather than writing code or running tests.
How it compares
Use instead of generic “what should I work on?” chat when you want repo-scoped issue facts and assignment filters.
Common Questions / FAQ
Who is my-issues for?
Solo builders and small teams who track work in GitHub Issues and want the agent to summarize their assigned queue.
When should I use my-issues?
At the start of a Build work session, before picking a branch, or when you need a prioritized view of assigned open issues.
Is my-issues safe to install?
Check the Security Audits panel on this Prism page; the skill reads repository and issue data via your connected GitHub context—avoid on untrusted forks.
SKILL.md
READMESKILL.md - My Issues
Search the current repo (using #githubRepo for the repo info) and list any issues you find (using #list_issues) that are assigned to me. Suggest issues that I might want to focus on based on their age, the amount of comments, and their status (open/closed).