メニュー
Retrieve GitHub issue information using the GitHub CLI (gh). USE FOR: viewing a specific issue by number, searching issues by topic or keyword, listing open/closed issues, and summarizing issue details. DO NOT USE FOR: creating issues (use issue-writer), commenting on issues, or closing issues.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | issue-reader |
| description | Retrieve GitHub issue information using the GitHub CLI (gh). USE FOR: viewing a specific issue by number, searching issues by topic or keyword, listing open/closed issues, and summarizing issue details. DO NOT USE FOR: creating issues (use issue-writer), commenting on issues, or closing issues. |
| compatibility | Requires GitHub CLI (gh) authenticated to the target repository. Works on Windows (PowerShell), macOS, and Linux (bash/zsh). |
Verify gh is available and authenticated:
gh auth status
If not authenticated, instruct the user to run:
gh auth login
Always use the repository of the current workspace. Detect it automatically from the Git remote before running any gh command and store it for reuse:
git remote get-url origin
If the command exits with a non-zero code or returns no output, stop and tell the user: "No Git remote named origin was found in this workspace. Please run this skill from inside the repository you want to query."
Do not ask the user to provide or override the repository. All gh commands in this skill must use the detected owner/repo via --repo owner/repo so they always target the current workspace repository regardless of the shell's working directory.
Determine what the user wants based on their input:
| User provides | Mode |
|---|---|
An issue number (e.g., #42 or 42) | View by number |
| A keyword, topic, or description | Search by topic |
| No specific issue — wants an overview | List issues |
Fetch the full details of a single issue:
gh issue view 42 --repo owner/repo
To get machine-readable JSON (useful for further processing):
gh issue view 42 --repo owner/repo --json number,title,body,state,labels,assignees,milestone,createdAt,updatedAt,url
Show the issue in the browser:
gh issue view 42 --repo owner/repo --web
Output summary to present to the user:
| Field | Description |
|---|---|
number | Issue number |
title | Issue title |
state | OPEN or CLOSED |
labels | Assigned labels |
assignees | Assigned users |
milestone | Associated milestone |
body | Full issue description |
url | Direct link |
Use --search to filter issues by keyword, label, assignee, or state. The search query supports GitHub search syntax. All commands target the current workspace repository.
Search by keyword:
gh issue list --repo owner/repo --search "<keyword>"
Search open issues only (default):
gh issue list --repo owner/repo --state open --search "<keyword>"
Search closed issues:
gh issue list --repo owner/repo --state closed --search "<keyword>"
Search by label:
gh issue list --repo owner/repo --label "bug" --search "<keyword>"
Limit results (default is 30):
gh issue list --repo owner/repo --search "<keyword>" --limit 10
Output as JSON for structured processing:
gh issue list --repo owner/repo --search "<keyword>" \
--json number,title,state,labels,assignees,url
All commands target the current workspace repository.
All open issues:
gh issue list --repo owner/repo
All issues (open and closed):
gh issue list --repo owner/repo --state all
Issues assigned to a specific user:
gh issue list --repo owner/repo --assignee "username"
Issues with a specific label:
gh issue list --repo owner/repo --label "enhancement"
Issues for a specific milestone:
gh issue list --repo owner/repo --milestone "v1.0"
For a single issue (view mode): Present the key fields in a readable summary. Include the direct URL at the end.
For a list or search result: Present as a markdown table with columns: #, Title, State, Labels, URL. Limit to the most relevant results. If the list is long, ask the user if they want to narrow the search.
When using --json, available fields include:
| Field | Type | Description |
|---|---|---|
number | int | Issue number |
title | string | Issue title |
body | string | Issue description (markdown) |
state | string | OPEN or CLOSED |
labels | array | Label names |
assignees | array | GitHub usernames |
milestone | object | Milestone title and due date |
author | object | Issue author login |
comments | array | Issue comments |
createdAt | string | ISO 8601 creation date |
updatedAt | string | ISO 8601 last update date |
closedAt | string | ISO 8601 close date (if closed) |
url | string | HTML URL of the issue |
| Error | Fix |
|---|---|
gh: command not found | Install GitHub CLI: https://cli.github.com |
You are not logged into any GitHub hosts | Run gh auth login |
Could not resolve to an issue | Verify the issue number exists; run gh issue list to confirm |
Repository not found | Ask the user to verify the owner/repo slug and re-run with --repo "<corrected-owner/repo>" |
Permission denied | Ensure the authenticated user has read access to the repository |
No results from --search | Broaden the query, remove filters, or try --state all |
Author, extend, and review BitBlazor library components — accessible, Bootstrap Italia-styled Blazor UI kit components for .NET 9+. USE FOR: creating a new Bit component, extending an existing component, adding a form field, reviewing component markup or parameters, writing bUnit tests for a component. DO NOT USE FOR: unrelated stacks or building Blazor applications with BitBlazor (not authoring the library itself). INVOKES: inspect the repository context, edit targeted files, and run relevant build and test commands when changes are made.
Create GitHub issues using the GitHub CLI (gh). USE FOR: opening a new issue, filing a bug report, requesting a feature, creating a task with labels, assignees, and milestones. DO NOT USE FOR: listing issues (use gh issue list), commenting on PRs, or pushing code changes.