GitHub Skill
Quick start
Goal: operate on GitHub-hosted state directly when repository facts, PR state, issues, releases, or remote file changes matter.
Reference notes: skills/github-skill/references/github-skill.md
Common read workflows
- Repository contents:
get_file_contents, list_branches, list_commits
- PRs:
pull_request_read, list_pull_requests, search_pull_requests
- Issues:
issue_read, list_issues, search_issues
- Discovery:
search_code, search_repositories, search_users
- Releases/tags:
get_latest_release, list_releases, list_tags
Common write workflows
- Issues and PR comments:
issue_write, add_issue_comment, reply_to_pull_request_comment
- PR review flow: create pending review → add review comments → submit review
- Remote file changes:
create_or_update_file, push_files, delete_file
- Branching and PRs:
create_branch, create_pull_request, update_pull_request
Workflow tips
- Prefer read APIs first to confirm remote state.
- Use search APIs when the target repo, PR, or symbol is not exact.
- Use review-specific tools for review comments; use issue comments only for discussion.
- For existing file updates, fetch the current SHA first.
High-risk actions
Require explicit user confirmation before:
- merging PRs
- deleting files, versions, or repos
- pushing remote file changes on important branches
- creating branches/PRs on the user’s behalf if intent is ambiguous
References
- Condensed notes:
skills/github-skill/references/github-skill.md
1---2name: github-skill3description: Use GitHub MCP for remote repository state: files, branches, commits, issues, pull requests, reviews, releases, and code search on GitHub. Use it when the task is centered on GitHub-hosted data, rather than a local checkout or IDE session.4---56# GitHub Skill78## Quick start910Goal: operate on GitHub-hosted state directly when repository facts, PR state, issues, releases, or remote file changes matter.1112Reference notes: `skills/github-skill/references/github-skill.md`1314## Common read workflows1516- Repository contents: `get_file_contents`, `list_branches`, `list_commits`17- PRs: `pull_request_read`, `list_pull_requests`, `search_pull_requests`18- Issues: `issue_read`, `list_issues`, `search_issues`19- Discovery: `search_code`, `search_repositories`, `search_users`20- Releases/tags: `get_latest_release`, `list_releases`, `list_tags`2122## Common write workflows2324- Issues and PR comments: `issue_write`, `add_issue_comment`, `reply_to_pull_request_comment`25- PR review flow: create pending review → add review comments → submit review26- Remote file changes: `create_or_update_file`, `push_files`, `delete_file`27- Branching and PRs: `create_branch`, `create_pull_request`, `update_pull_request`2829## Workflow tips30311. Prefer read APIs first to confirm remote state.322. Use search APIs when the target repo, PR, or symbol is not exact.333. Use review-specific tools for review comments; use issue comments only for discussion.344. For existing file updates, fetch the current SHA first.3536## High-risk actions3738Require explicit user confirmation before:39- merging PRs40- deleting files, versions, or repos41- pushing remote file changes on important branches42- creating branches/PRs on the user’s behalf if intent is ambiguous4344## References4546- Condensed notes: `skills/github-skill/references/github-skill.md`
ry-run