github-code

This skill enables agents to interact with GitHub repositories using git and gh commands for implementation, code investigation, branching, pull request…

by SentryOfficial publisherNot reviewed

Identity proven by GitHub's verified organisation badge (getsentry)

Agents: Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode, claude.ai and API
License: Apache-2.0 (permissive)
Pin: 1745a29pinned Oct 9, 2026
Context cost: about 580 tokenswhen the skill loads
GitHub stars: 367on getsentry/junior
Scripts: None found

What it does

“Work with GitHub repositories, source code, branches, commits, pull requests, reviews, diffs, CI, and repository credentials. Use for implementation, source investigation, clone/fetch/branch workflows, PR creation or updates, review feedback, GitHub Actions checks, and repository permission failures. Prefer this skill for repository tasks even when they concern a Sentry product.”

The author's description, from SKILL.md

Generated summary from the skill's own text

This skill enables agents to interact with GitHub repositories using git and gh commands for implementation, code investigation, branching, pull request management, and CI workflows. It provides specialized functions for creating and updating pull requests, submitting reviews, and cloning repositories while enforcing safe practices around destructive operations and permission handling.

When to use it

Implementing code changes and managing Git workflows in repositories
Creating, updating, or reviewing pull requests on GitHub
Investigating source code and comparing branches or commits
Resolving GitHub permission failures or checking CI status

When not to

When destructive operations like force-pushing or branch deletion are necessary
If using GitHub Actions or other CI tools directly outside repository context
For non-Git version control systems or non-GitHub platforms

Install

These commands install from the publisher's repository and need no account.

skills CLI

npx skills add getsentry/junior --skill github-code

Installs from the repository's default branch, which may have changed since the commit we checked.

GitHub CLI 2.90 or later

gh skill install getsentry/junior github-code@1745a298365f0f001db0b3eec6de8a8347e0f6d9

Installs the commit we checked (1745a29).

Copy by hand

Download the folder at 1745a29 and put it in .claude/skills/github-code for Claude Code and in .agents/skills/github-code for Codex, Cursor, Gemini CLI, GitHub Copilot and OpenCode.

Skill folder on GitHub at 1745a29

Claude Code plugin

/plugin install sentry@claude-plugins-official

The publisher's plugin in Claude's official marketplace. It may hold more than this skill, and we have not pinned it.

Claude Code plugin

/plugin install sentry-cli@claude-plugins-official

The publisher's plugin in Claude's official marketplace. It may hold more than this skill, and we have not pinned it.

Copy for your agent

A prompt for any coding agent. It installs this skill from GitHub at the pinned commit, copies the files as they are, and runs nothing unless you ask.

Prompt

Install the agent skill "github-code" by Sentry.

Source, pinned to commit 1745a298365f0f001db0b3eec6de8a8347e0f6d9:
https://github.com/getsentry/junior/tree/1745a298365f0f001db0b3eec6de8a8347e0f6d9/packages/junior-github/skills/github-code

1. Download that folder at exactly this commit. Do not use the default branch.
2. Copy every file unchanged, keeping the folder structure, into .claude/skills/github-code/ for Claude Code and .agents/skills/github-code/ for Codex, Cursor, Gemini CLI, GitHub Copilot and OpenCode. Create the folders if they do not exist.
3. Do not edit the files, and do not run any script in the folder unless I ask you to.
4. When you are done, list the files you copied and where you put them.

Listing and checks: https://www.agentnative.dev/skills/sentry/github-code

SKILL.md at the pin

---
name: github-code
description: Work with GitHub repositories, source code, branches, commits, pull requests, reviews, diffs, CI, and repository credentials. Use for implementation, source investigation, clone/fetch/branch workflows, PR creation or updates, review feedback, GitHub Actions checks, and repository permission failures. Prefer this skill for repository tasks even when they concern a Sentry product.
---

# GitHub code

Use `git` and `gh` for repository work.

| Action                          | Tool / command                                                           |
| ------------------------------- | ------------------------------------------------------------------------ |
| Create PR                       | `github_createPullRequest` (not `gh pr create`)                          |
| Update PR title/body/base/state | `github_updatePullRequest`                                               |
| Submit PR review                | `github_submitPullRequestReview`                                         |
| Resolve review thread           | `github_resolvePullRequestReviewThread`                                  |
| Clone missing repo              | `github_cloneRepository`; on Workspace match error use `switchWorkspace` |

## Open when needed

| Need                          | Read                                                                                   |
| ----------------------------- | -------------------------------------------------------------------------------------- |
| Commands and permissions      | [references/api-surface.md](references/api-surface.md)                                 |
| Edit, verify, and open a PR   | [references/workflow.md](references/workflow.md)                                       |
| Command or permission failure | [references/troubleshooting-workarounds.md](references/troubleshooting-workarounds.md) |

## Always

- Use the requested repo. Otherwise read `github.repo` with standalone `jr-rpc config get github.repo`.
- Pass `--repo owner/repo` to `gh`. Use `git -C PATH` for local repos.
- Read each applicable `AGENTS.md` before edits.
- Keep unrelated work. Never force-push, delete refs, or make destructive merges.
- Use repository evidence. Report only checks you ran.
- Push before `github_createPullRequest`. Never ask for a token for bot pushes.
- When an error names a tool, use it. Change permissions only when GitHub rejected the request.
- Stop for an unclear target, missing access, destructive work, or a GitHub permission failure.
- Unless the user opts out, push completed work and open a draft PR.
- Report repo, branch, PR, checks, and skipped checks.

Do not install or repair the GitHub plugin from this skill.

From getsentry/junior at 1745a29, shown as plain text under its license: Apache-2.0 (permissive). The license text is in LICENSE.

View SKILL.md on GitHub at 1745a29

Files

SKILL.md2.7 KB · 933d7b27eb87
SPEC.md1.8 KB · d96c196a7b7f
references/
api-surface.md5.4 KB · d2bd025c4849
troubleshooting-workarounds.md3.8 KB · 6ed3ad217d4c
workflow.md2.7 KB · 50c0947121cc

5 files, 16 KB in total. Each file has a sha256 in the pin's manifest; the first 12 characters are shown.

Skill folder on GitHub at 1745a29

All 50 skills from Sentry

github-code

What it does

When to use it

When not to

Install

Copy for your agent

SKILL.md at the pin

Files

More from Sentry

claude-settings-audit

commit

django-access-review

django-perf-review

iterate-pr

pr-writer

self-update

merge-pr

maintainer-review

maintainer-review

dd-file-issue

create-pr

What it does

When to use it

When not to

Install

Copy for your agent

SKILL.md at the pin

Files

More from Sentry

Related in Coding workflow