GitHub for Claude, Cursor, ChatGPT & agents

GitHub — search repos and code, list your repos / orgs / branches / commits, file and triage issues, open / list / get / review / comment-on / merge pull requests, read files at any ref, trigger Ac...

curl -fsSL https://syncorelabs.ai/install.sh | sh

What it does

GitHub — search repos and code, list your repos / orgs / branches / commits, file and triage issues, open / list / get / review / comment-on / merge pull requests, read files at any ref, trigger Actions workflows and inspect runs, create and list releases. Use when the user mentions GitHub, GH, repo, PR, pull request, issue, branch, commit, workflow, Actions, code search, release, tag, or wants to manage / inspect / ship work in GitHub.

The GitHub skill is one of 75+ pre-wired Syncore integrations that any MCP-compatible client — Claude Desktop, Claude Code, Cursor, Windsurf, Codex CLI, and ChatGPT desktop — can call out of the box. You don't configure MCP servers or copy API keys into a JSON file; the Syncore daemon discovers the skill at startup and exposes its tools to whichever AI client is running.

Sample prompts

Once Syncore is installed and GitHub is connected, ask your agent something like:

• “List all open PRs assigned to me across my repos.”
• “Read the README of ericwang915/Syncore and summarize the architecture.”
• “Create an issue in talon: title 'Skill catalog rebuild', body the spec from this thread.”

Tools available (23)

• github__search_repos

  Search / find GitHub repositories using GitHub search syntax (e.g. 'language:python stars:>100', 'org:vercel topic:nextjs'). Use when the user wants to discover repos by language, popularity, owner, or topic.

• github__list_issues

  List GitHub issues in a repository (open / closed / all). Use when the user wants to see the bug / feature / triage queue, audit recent issues, or find tickets to work on. Repo in owner/name form.

• github__create_issue

  File / open / create a new GitHub issue in a repo with title and Markdown body. Use when the user wants to log a bug, capture a feature request, or open a tracking issue.

• github__close_issue

  Close a GitHub issue. GitHub's REST API doesn't allow hard-deleting issues (admin-only via the web UI); closing is the standard cleanup path. Optionally set `reason` to 'completed' or 'not_planned' to populate the state_reason field. Idempotent on already-closed issues.

• github__create_pr

  Open / create / file a new pull request from head branch to base branch (default main) with title and Markdown body. Use when the user wants to ship a change, open a PR for review, or merge work between branches. Cross-fork supported via user:branch.

• github__close_pr

  Close a pull request WITHOUT merging it. Use when the agent wants to drop a PR (superseded, no longer needed, accidentally opened). For merging an approved PR use the merge_pr tool. Idempotent on already-closed PRs.

• github__read_file

  Read / fetch a file or list a directory from a GitHub repository at any branch / tag / commit SHA (ref). Use when the user wants to inspect code, peek at a file's contents, or audit a directory listing.

• github__list_actions

  List recent GitHub Actions workflow runs for a repo with status (success / failure / in_progress). Use when the user wants to check 'did CI pass', debug a failing build, or audit recent runs. Optional workflow_id to filter to one workflow file.

• github__trigger_workflow

  Trigger / dispatch a GitHub Actions workflow_dispatch run on a branch / tag with optional inputs. Use when the user wants to manually fire a deploy / release / cron-like workflow.

• github__search_code

  Search code across GitHub (or one repo) using GitHub code-search syntax. Use when the user wants to find a function, class, or string across the public ecosystem or inside a specific repo. Optional repo filter (owner/name).

• github__create_release

  Create / publish a new GitHub release with a tag (created if missing), title, Markdown notes, and draft / prerelease flags. Use when the user wants to ship a version, cut a release, or publish release notes.

• github__list_releases

  List GitHub releases for a repo (most recent first). Use when the user wants to see version history, what shipped lately, or pull release notes.

• github__list_my_repos

  List GitHub repositories owned by or accessible to the authenticated user — owner / collaborator / org-member. Use when the user wants to browse 'my repos' or you need an owner/name reference. Supports visibility filter (all / public / private), sort.

• github__list_my_orgs

  List GitHub organizations the authenticated user is a member of. Use when the user wants to see their orgs or you need an org login for downstream calls.

• github__list_prs

  List GitHub pull requests for a repo (open / closed / all), optionally filtered by head / base branch. Use when the user wants to triage open PRs, see recently merged work, or find their own PRs to babysit.

• github__get_pr

  Fetch / read full details of one GitHub pull request — title, body, branches, mergeable state, review state, CI checks. Use when the user wants the complete picture of a PR before commenting / merging.

• github__list_pr_reviews

  List submitted reviews on a GitHub PR (approve / request-changes / comment) with reviewer + state. Use when the user wants to see who has reviewed and what they said.

• github__list_pr_comments

  List both issue-level and inline review-line comments on a GitHub PR. Use when the user wants to read review feedback, find unresolved comments, or summarize discussion.

• github__create_pr_review

  Submit / post / publish a PR review on GitHub — APPROVE, REQUEST_CHANGES, or COMMENT, with Markdown body. Use when the user wants to approve a PR, block it, or leave overall review feedback.

• github__comment_on_pr

  Post / add an issue-level comment on a GitHub PR (Markdown). Use when the user wants to drop a note on a PR without submitting a full review.

• github__merge_pr

  Merge / land / squash / rebase a GitHub PR using merge / squash / rebase method. Use when the user wants to land an approved PR. Optional commit_title and commit_message.

• github__list_branches

  List branches in a GitHub repo, optionally filtered to protected only. Use when the user wants to see what branches exist or pick a branch ref.

• github__list_commits

  List GitHub commits on a branch / tag / SHA, optionally filtered by path, author, since/until ISO timestamps. Use when the user wants to see recent commits, find who touched a file, or audit history in a date window.

How to connect

GitHub needs a one-click OAuth grant to talk to github. Connect it from the Syncore dashboard:

1. Run curl -fsSL https://syncorelabs.ai/install.sh | sh on macOS / Linux (or the PowerShell command on Windows).
2. Run syncore login to create your account and a device-bound encryption key.
3. Visit syncorelabs.ai/connect and authorize GitHub.
4. Run syncore update to sync the skill + credentials to every installed AI client.

Pricing

Free at every Syncore tier. Connect your account once at /connect; the OAuth or API-key credential stays encrypted on your machine and syncs to your other devices via the Syncore vault.

See the full Syncore pricing breakdown — Free $0/mo, Pro $29/mo, Ultra $99/mo — on the homepage.