github

# GitHub Work with GitHub through the connected `github` MCP server. Prefer its tools over shelling out to `gh` or `git` — they return structured data and work without a local checkout. Use this core skill to orient the repository and route the request. Use `review-follow-up` for review threads, `ci-debug` for failing Actions checks, and `publish-changes` for commit/push/PR work. Do not blend a read-only inspection request into a publishing workflow. ## Before you start Confirm the server is connected. If its tools are unavailable, say so and stop rather than silently falling back to guesswork; the user connects it from **Settings → Plugins → GitHub**. Establish the target repository once, from the user's words or the current project's `origin` remote, and reuse it. Do not guess an owner or repo name. ## Reading - Read the pull request or issue body **and** its comments before forming an opinion. Review threads carry the decisions; the description is often stale. - For a PR, read the diff before the discussion. Someone's summary of a change is not the change. - Quote file and line when you reference code, so the user can jump to it. - Resolve repository, pull request, issue, check, and ref identifiers once and reuse the exact identifiers. If more than one target plausibly matches, ask rather than acting on the first search result. ## Writing Anything that other people will see — a comment, a review, a label change, a merge — is outward-facing. Confirm the exact t...