원클릭으로 Manus에서 모든 스킬 실행

시작하기

github

스타0

포크0

업데이트2026년 7월 10일 16:54

Use the `gh` CLI for issues, pull requests, Actions runs, and GitHub API queries.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

d9beuD

d9beuD/genealogist-frontend

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

GitHub Skill

Use the gh CLI to interact with GitHub. Always specify --repo owner/repo when not in a git directory, or use URLs directly.

When to Use

When the user asks about GitHub issues, pull requests, workflow runs, or CI failures.
When you need gh issue, gh pr, gh run, or gh api from the command line.

Pull Requests

Check CI status on a PR:

gh pr checks 55 --repo owner/repo

List recent workflow runs:

gh run list --repo owner/repo --limit 10

View a run and see which steps failed:

gh run view <run-id> --repo owner/repo

View logs for failed steps only:

gh run view <run-id> --repo owner/repo --log-failed

Debugging a CI Failure

Follow this sequence to investigate a failing CI run:

Check PR status — identify which checks are failing:
```
gh pr checks 55 --repo owner/repo
```
List recent runs — find the relevant run ID:
```
gh run list --repo owner/repo --limit 10
```
View the failed run — see which jobs and steps failed:
```
gh run view <run-id> --repo owner/repo
```
Fetch failure logs — get the detailed output for failed steps:
```
gh run view <run-id> --repo owner/repo --log-failed
```

API for Advanced Queries

The gh api command is useful for accessing data not available through other subcommands.

Get PR with specific fields:

gh api repos/owner/repo/pulls/55 --jq '.title, .state, .user.login'

JSON Output

Most commands support --json for structured output. You can use --jq to filter:

gh issue list --repo owner/repo --json number,title --jq '.[] | "\(.number): \(.title)"'

이 저장소의 다른 Skills

같은 저장소

commit

d9beuD/genealogist-frontend

ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional commit format and issue references. Trigger on any commit, git commit, save changes, or commit message task.

2026-07-100

create-branch

d9beuD/genealogist-frontend

Create a git branch following Sentry naming conventions. Use when asked to "create a branch", "new branch", "start a branch", "make a branch", "switch to a new branch", or when starting new work on the default branch.

2026-07-100

create-pr

d9beuD/genealogist-frontend

Alias for sentry-skills:pr-writer. Use when users explicitly ask for "create-pr" or reference the legacy skill name. Redirects to the canonical PR writing workflow.

2026-07-100

subagent-driven-development

d9beuD/genealogist-frontend

Use when executing implementation plans with independent tasks in the current session

2026-07-100

subagent-orchestrator

d9beuD/genealogist-frontend

Coordinate quota-aware parallel subagents for large, multi-file Antigravity tasks.

2026-07-100

tailwind-design-system

d9beuD/genealogist-frontend

Build production-ready design systems with Tailwind CSS, including design tokens, component variants, responsive patterns, and accessibility.

2026-07-100

name	github
description	Use the `gh` CLI for issues, pull requests, Actions runs, and GitHub API queries.
risk	safe
source	Dimillian/Skills (MIT)
date_added	2026-03-25

GitHub Skill

Use the gh CLI to interact with GitHub. Always specify --repo owner/repo when not in a git directory, or use URLs directly.

When to Use

When the user asks about GitHub issues, pull requests, workflow runs, or CI failures.
When you need gh issue, gh pr, gh run, or gh api from the command line.

Pull Requests

Check CI status on a PR:

gh pr checks 55 --repo owner/repo

List recent workflow runs:

gh run list --repo owner/repo --limit 10

View a run and see which steps failed:

gh run view <run-id> --repo owner/repo

View logs for failed steps only:

gh run view <run-id> --repo owner/repo --log-failed

Debugging a CI Failure

Follow this sequence to investigate a failing CI run:

Check PR status — identify which checks are failing:
```
gh pr checks 55 --repo owner/repo
```
List recent runs — find the relevant run ID:
```
gh run list --repo owner/repo --limit 10
```
View the failed run — see which jobs and steps failed:
```
gh run view <run-id> --repo owner/repo
```
Fetch failure logs — get the detailed output for failed steps:
```
gh run view <run-id> --repo owner/repo --log-failed
```

API for Advanced Queries

The gh api command is useful for accessing data not available through other subcommands.

Get PR with specific fields:

gh api repos/owner/repo/pulls/55 --jq '.title, .state, .user.login'

JSON Output

Most commands support --json for structured output. You can use --jq to filter:

gh issue list --repo owner/repo --json number,title --jq '.[] | "\(.number): \(.title)"'