gh-cli
GitHub CLI 参考
此技能为 GitHub CLI (gh) 提供全面的参考文档,使 AI 助手能够从命令行执行 GitHub 操作,包括仓库、议题、拉取请求、Actions 等。
스킬 ZIP 다운로드
Claude에서 업로드
설정 → 기능 → 스킬 → 스킬 업로드로 이동
토글을 켜고 사용 시작
테스트해 보기
"gh-cli" 사용 중입니다. 显示最近的 5 个拉取请求
예상 결과:
- Pull Request #123: Add user authentication
- Status: open | Reviews: 2 approved
- Pull Request #122: Fix login bug
- Status: merged | Reviews: 1 approved
- Pull Request #121: Update dependencies
- Status: closed | Reviews: 0
"gh-cli" 사용 중입니다. 创建一个标题为 'Memory leak in dashboard' 的议题
예상 결과:
Issue created successfully!
https://github.com/owner/repo/issues/456
Title: Memory leak in dashboard
State: open
Created at: 2026-03-13T08:15:00Z
보안 감사
안전This is a documentation/reference skill for the GitHub CLI. All static scanner findings are false positives. The skill contains only markdown documentation with command examples - no executable code, no credential access, no file system manipulation. The detected patterns (external_commands, network, filesystem, env_access) are all legitimate documentation content showing how to use the gh CLI tool.
중간 위험 문제 (1)
품질 점수
만들 수 있는 것
开发工作流自动化
直接从 AI 对话中自动化常见的 GitHub 操作,如创建议题、管理 PR 和检查工作流状态。
仓库管理
通过 CLI 使用自然语言命令创建、克隆、分支和管理 GitHub 仓库。
CI/CD 集成
通过 CLI 监视和管理 GitHub Actions 工作流、检查构建状态和下载产物。
이 프롬프트를 사용해 보세요
Use the gh-cli skill to show me the status of the current repository including open issues and PRs.
Use gh-cli to create a pull request with title 'Add new feature' and description from the file feature.txt.
Use gh-cli to list the last 10 open issues labeled 'bug' in the owner/repo repository.
Use gh-cli to check the status of the latest GitHub Actions workflow run and show any failed jobs.
모범 사례
- Always authenticate with gh auth login before performing operations
- Use --json flag for machine-readable output that can be parsed
- Specify repository with --repo owner/repo when not in a git repository
- Use --web flag to open GitHub web interface when visual confirmation is needed
피하기
- Running gh commands without first verifying authentication status
- Using personal access tokens in command line (use gh auth login instead)
- Ignoring errors from gh commands assuming they succeeded
- Not checking rate limits before making bulk API calls