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

issue-review

スター19,250

フォーク630

更新日2026年7月17日 13:27

Investigate, review, and fix GitHub issues. Use when a request references a GitHub issue URL or number and asks for analysis, root-cause location, implementation, or a fix commit.

インストール

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

Manusで実行

ソース

Nagi-ovo

Nagi-ovo/voyager

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

ダウンロード

Manusで実行

Issue Review

Begin with gh issue view <number-or-url> --comments (add --repo owner/repo when needed). Read the actual issue before locating the cause in the repository.
If implementing the fix, validate it and create one scoped commit whose message or footer contains Closes #<number> or Fixes #<number>.
Before finishing, verify the committed file scope and the closing keyword with git show --stat --format=fuller HEAD.
After the fix, draft and, when authorized, post a short issue reply saying it is fixed and will be available in the next version. Verify the issue is closed; if needed, close it with gh issue close.

このリポジトリの他の Skills

同じリポジトリ

release

Nagi-ovo/voyager

Cut or recover a Voyager release, including issue triage, verification, versioning, the 10-locale in-product changelog, commit and tag creation, GitHub Actions monitoring, Chrome Web Store, Firefox AMO, Edge Add-ons, and the signed/notarized Safari DMG with Sparkle updates. Use for “发版”, “release”, “bump”, “ship vX.Y.Z”, store retries, or Safari release failures.

2026-07-2019.3k

update-safari-extension

Nagi-ovo/voyager

Safely build, reload, install, and verify Voyager's Safari web extension without disturbing extension storage, permissions, or the user's signed app. Use for Safari UI or runtime testing, refreshing dist_safari after TypeScript or CSS changes, testing Swift or native messaging changes, diagnosing stale Safari resources, or validating a signed direct-distribution build.

2026-07-1819.3k

name	issue-review
description	Investigate, review, and fix GitHub issues. Use when a request references a GitHub issue URL or number and asks for analysis, root-cause location, implementation, or a fix commit.

Issue Review

Begin with gh issue view <number-or-url> --comments (add --repo owner/repo when needed). Read the actual issue before locating the cause in the repository.
If implementing the fix, validate it and create one scoped commit whose message or footer contains Closes #<number> or Fixes #<number>.
Before finishing, verify the committed file scope and the closing keyword with git show --stat --format=fuller HEAD.
After the fix, draft and, when authorized, post a short issue reply saying it is fixed and will be available in the next version. Verify the issue is closed; if needed, close it with gh issue close.