원클릭으로 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.