ワンクリックでManusで任意のスキルを実行

gh-issue

スター0

フォーク0

更新日2026年3月16日 02:46

Operate GitHub issues with the `gh` CLI end-to-end. Use this skill whenever the user asks to create/list/view/search/update/comment/close/reopen/label/assign/triage issues, including Chinese requests like "提 issue", "查 issue", "关 issue", "加标签", or "批量处理 issue".

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

ximing

ximing/spark

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

GitHub `gh issue` Workflow Skill

Use this skill to turn natural language requests into safe, exact gh issue commands and execution steps.

What this skill is responsible for

Handle day-to-day issue operations using GitHub CLI.
Resolve repository context before running commands.
Prefer non-interactive command flags so automation is stable.
Provide concise action summaries with issue links and command results.

Trigger conditions

Activate this skill whenever the user asks for any of the following:

Create an issue from bug notes, TODOs, meeting notes, or markdown content.
List, search, or filter issues by state, label, assignee, author, or text.
View issue details/comments or fetch issue fields in JSON.
Edit title/body/labels/assignees/milestone.
Comment, close, reopen, lock, or unlock issues.
Triage stale issues or do batch issue maintenance.

Do not use this skill for pull-request-only tasks unless the user explicitly asks for both PR and issue workflows.

Preflight checklist

Before issue operations, run these checks in order:

Verify CLI is available:
- gh --version
Verify authentication:
- gh auth status
Resolve repository context:
- If user provided repo, use --repo owner/repo explicitly.
- Else, if inside a git repo, use current remote context.
- Else, request owner/repo from user.
Verify access:
- gh repo view --json nameWithOwner,viewerPermission

If auth or permissions fail, stop and show exact remediation command.

Core command templates

1) List and search issues

List open issues:
- gh issue list --state open --limit 50
Search with query syntax:
- gh issue list --search "label:bug is:open sort:updated-desc" --limit 100
JSON output for automation:
- gh issue list --state all --json number,title,state,labels,assignees,url,updatedAt

2) View issue details

Basic details:
- gh issue view <number>
Include comments:
- gh issue view <number> --comments
Structured fields:
- gh issue view <number> --json number,title,body,state,labels,assignees,comments,url

3) Create issue

Fast create:
- gh issue create --title "<title>" --body "<body>"
With labels/assignees/milestone:
- gh issue create --title "<title>" --body-file <body.md> --label bug --assignee <user> --milestone "<milestone>"
Against a specific repo:
- gh issue create --repo owner/repo --title "<title>" --body "<body>"

When body content is long, generate a temporary markdown file and use --body-file.

4) Edit issue

Update title/body:
- gh issue edit <number> --title "<new-title>" --body-file <body.md>
Labels:
- gh issue edit <number> --add-label bug --remove-label needs-info
Assignees:
- gh issue edit <number> --add-assignee <user> --remove-assignee <user>
Milestone:
- gh issue edit <number> --milestone "<milestone>"

5) Comment and state transitions

Add comment:
- gh issue comment <number> --body "<comment>"
Close with reason comment:
- gh issue close <number> --comment "<why closing>"
Reopen with context:
- gh issue reopen <number> --comment "<why reopening>"
Lock/unlock:
- gh issue lock <number> --reason resolved
- gh issue unlock <number>

Recommended workflows

Workflow A: Create issue from user text

Extract title candidates and concise problem statement.
Build body template:
- Background
- Current behavior
- Expected behavior
- Repro steps
- Scope/impact
- Acceptance criteria
Choose labels/assignee/milestone from user intent.
Run gh issue create ....
Return issue number + URL + next actions.

Workflow B: Triage inbox

Pull target set with gh issue list --search ... --json ....
Group by label/state/assignee.
Suggest edits before batch execution when impact is broad.
Apply edits with explicit commands.
Report changed issues in a compact table.

Workflow C: Batch updates (safe mode)

Preview target list first.
Execute updates in a loop only after preview:
- Example pattern:
  - gh issue list --search "label:needs-triage" --json number --jq '.[].number'
Apply one command per issue and capture failures.
Summarize success/failure counts.

Never run destructive or broad-scope batch operations without an explicit user request.

Output format for final response

Use this structure after completing commands:

Repo: owner/repo
Actions executed: short bullet list of command intents
Results:
- #123 - <state> - <url>
- #456 - <state> - <url>
Failures (if any): reason + retry command
Suggested next step: one practical follow-up

Error handling playbook

Not logged in:
- gh auth login
Wrong repo context:
- add --repo owner/repo
Permission denied:
- show viewerPermission from gh repo view and explain limitation
Missing issue number:
- run filtered list first and let user pick target
Validation/API errors:
- rerun command with minimal flags, then add fields incrementally

Practical examples

Example 1: "Create a bug issue"

User intent: "帮我提一个 issue，描述登录后首页白屏。"

Action outline:

Draft title: bug(web): blank home page after login
Draft structured body from user context.
Run:
- gh issue create --title "bug(web): blank home page after login" --body-file /tmp/issue-body.md --label bug

Example 2: "Find stale issues and close them with comment"

Preview stale targets:
- gh issue list --search "is:open updated:<2025-12-01 label:needs-info" --json number,title,url
After confirmation, close each issue with:
- gh issue close <number> --comment "Closing due to inactivity. Reopen if this is still relevant."

Quality bar

Commands must be executable as-is.
Repo context must be explicit when ambiguous.
Use JSON output when parsing is needed.
Responses must include URLs for all affected issues.
Keep user-facing summaries concise and actionable.

このリポジトリの他の Skills

同じリポジトリ

arch-review

ximing/spark

面向 Echoe 功能正确性审查技能。只要用户提到“架构评审、流程校验、功能实现是否正常、重复代码治理、权限/跨租户安全检查、将问题转为 GitHub issue”，就应立即启用。若发现可执行且已确认的问题，必须使用 `gh` CLI 按严格模板创建 issue。

2026-03-160

prd

ximing/spark

Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.

2026-03-160

name	gh-issue
description	Operate GitHub issues with the `gh` CLI end-to-end. Use this skill whenever the user asks to create/list/view/search/update/comment/close/reopen/label/assign/triage issues, including Chinese requests like "提 issue", "查 issue", "关 issue", "加标签", or "批量处理 issue".

GitHub `gh issue` Workflow Skill

Use this skill to turn natural language requests into safe, exact gh issue commands and execution steps.

What this skill is responsible for

Handle day-to-day issue operations using GitHub CLI.
Resolve repository context before running commands.
Prefer non-interactive command flags so automation is stable.
Provide concise action summaries with issue links and command results.

Trigger conditions

Activate this skill whenever the user asks for any of the following:

Create an issue from bug notes, TODOs, meeting notes, or markdown content.
List, search, or filter issues by state, label, assignee, author, or text.
View issue details/comments or fetch issue fields in JSON.
Edit title/body/labels/assignees/milestone.
Comment, close, reopen, lock, or unlock issues.
Triage stale issues or do batch issue maintenance.

Do not use this skill for pull-request-only tasks unless the user explicitly asks for both PR and issue workflows.

Preflight checklist

Before issue operations, run these checks in order:

Verify CLI is available:
- gh --version
Verify authentication:
- gh auth status
Resolve repository context:
- If user provided repo, use --repo owner/repo explicitly.
- Else, if inside a git repo, use current remote context.
- Else, request owner/repo from user.
Verify access:
- gh repo view --json nameWithOwner,viewerPermission

If auth or permissions fail, stop and show exact remediation command.

Core command templates

1) List and search issues

List open issues:
- gh issue list --state open --limit 50
Search with query syntax:
- gh issue list --search "label:bug is:open sort:updated-desc" --limit 100
JSON output for automation:
- gh issue list --state all --json number,title,state,labels,assignees,url,updatedAt

2) View issue details

Basic details:
- gh issue view <number>
Include comments:
- gh issue view <number> --comments
Structured fields:
- gh issue view <number> --json number,title,body,state,labels,assignees,comments,url

3) Create issue

Fast create:
- gh issue create --title "<title>" --body "<body>"
With labels/assignees/milestone:
- gh issue create --title "<title>" --body-file <body.md> --label bug --assignee <user> --milestone "<milestone>"
Against a specific repo:
- gh issue create --repo owner/repo --title "<title>" --body "<body>"

When body content is long, generate a temporary markdown file and use --body-file.

4) Edit issue

Update title/body:
- gh issue edit <number> --title "<new-title>" --body-file <body.md>
Labels:
- gh issue edit <number> --add-label bug --remove-label needs-info
Assignees:
- gh issue edit <number> --add-assignee <user> --remove-assignee <user>
Milestone:
- gh issue edit <number> --milestone "<milestone>"

5) Comment and state transitions

Add comment:
- gh issue comment <number> --body "<comment>"
Close with reason comment:
- gh issue close <number> --comment "<why closing>"
Reopen with context:
- gh issue reopen <number> --comment "<why reopening>"
Lock/unlock:
- gh issue lock <number> --reason resolved
- gh issue unlock <number>

Recommended workflows

Workflow A: Create issue from user text

Extract title candidates and concise problem statement.
Build body template:
- Background
- Current behavior
- Expected behavior
- Repro steps
- Scope/impact
- Acceptance criteria
Choose labels/assignee/milestone from user intent.
Run gh issue create ....
Return issue number + URL + next actions.

Workflow B: Triage inbox

Pull target set with gh issue list --search ... --json ....
Group by label/state/assignee.
Suggest edits before batch execution when impact is broad.
Apply edits with explicit commands.
Report changed issues in a compact table.

Workflow C: Batch updates (safe mode)

Preview target list first.
Execute updates in a loop only after preview:
- Example pattern:
  - gh issue list --search "label:needs-triage" --json number --jq '.[].number'
Apply one command per issue and capture failures.
Summarize success/failure counts.

Never run destructive or broad-scope batch operations without an explicit user request.

Output format for final response

Use this structure after completing commands:

Repo: owner/repo
Actions executed: short bullet list of command intents
Results:
- #123 - <state> - <url>
- #456 - <state> - <url>
Failures (if any): reason + retry command
Suggested next step: one practical follow-up

Error handling playbook

Not logged in:
- gh auth login
Wrong repo context:
- add --repo owner/repo
Permission denied:
- show viewerPermission from gh repo view and explain limitation
Missing issue number:
- run filtered list first and let user pick target
Validation/API errors:
- rerun command with minimal flags, then add fields incrementally

Practical examples

Example 1: "Create a bug issue"

User intent: "帮我提一个 issue，描述登录后首页白屏。"

Action outline:

Draft title: bug(web): blank home page after login
Draft structured body from user context.
Run:
- gh issue create --title "bug(web): blank home page after login" --body-file /tmp/issue-body.md --label bug

Example 2: "Find stale issues and close them with comment"

Preview stale targets:
- gh issue list --search "is:open updated:<2025-12-01 label:needs-info" --json number,title,url
After confirmation, close each issue with:
- gh issue close <number> --comment "Closing due to inactivity. Reopen if this is still relevant."

Quality bar

Commands must be executable as-is.
Repo context must be explicit when ambiguous.
Use JSON output when parsing is needed.
Responses must include URLs for all affected issues.
Keep user-facing summaries concise and actionable.

gh-issue

GitHub gh issue Workflow Skill

What this skill is responsible for

Trigger conditions

Preflight checklist

Core command templates

1) List and search issues

2) View issue details

3) Create issue

4) Edit issue

5) Comment and state transitions

Recommended workflows

Workflow A: Create issue from user text

Workflow B: Triage inbox

Workflow C: Batch updates (safe mode)

Output format for final response

Error handling playbook

Practical examples

Example 1: "Create a bug issue"

Example 2: "Find stale issues and close them with comment"

Quality bar

このリポジトリの他の Skills

このリポジトリの他の Skills

GitHub gh issue Workflow Skill

What this skill is responsible for

Trigger conditions

Preflight checklist

Core command templates

1) List and search issues

2) View issue details

3) Create issue

4) Edit issue

5) Comment and state transitions

Recommended workflows

Workflow A: Create issue from user text

Workflow B: Triage inbox

Workflow C: Batch updates (safe mode)

Output format for final response

Error handling playbook

Practical examples

Example 1: "Create a bug issue"

Example 2: "Find stale issues and close them with comment"

Quality bar

GitHub `gh issue` Workflow Skill

GitHub `gh issue` Workflow Skill