AGENT SKILL

github-code

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.

适用职业开发工程师
License 许可
Apache-2.0
所属仓库
getsentry/junior
最近更新
2026-11-11
Stars
★ 411
Forks
45

01 前言 Front Matter

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.

02 资源文件 4

03 SKILL.md 正文

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
Mark PR ready / draft github_updatePullRequest with draft: false / draft: true
Submit PR review github_submitPullRequestReview
Comment on PR / reply in thread github_commentOnPullRequest (in_reply_to for a thread reply)
Resolve review thread github_resolvePullRequestReviewThread
Clone missing repo github_cloneRepository (not git clone or gh repo clone); on Workspace match error use switchWorkspace

Open when needed

Need Read
Commands and permissions references/api-surface.md
Edit, verify, and open a PR references/workflow.md
Command, permission, or CI failure 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 delete refs or make destructive merges.
  • Force-push only with --force-with-lease, and only to branches Junior pushed or the requester named.
  • 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.
  • Code changes always end in a pushed branch and a PR. Do not ask whether to open one. Skip it only when the user opts out or asks for investigation only.
  • Open the PR ready for review when the work is complete and the checks pass. Open a draft when work, checks, or decisions remain. A scope or follow-up question is not a reason to stop: open the PR, and name the question in the PR body and the report.
  • Link the PR. Mention checks only when they failed or were skipped.

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

04 同仓库更多 Skills

getsentry
getsentry/junior

junior

Build, review, or update Junior extension skills and plugins. Use when users ask to create a Junior SKILL.md, app skill, plugin, plugin.yaml, packaged plugin, MCP-backed plugin, OAuth or credentialed plugin, or to validate Junior extension files. Do not use for ordinary Junior usage, provider workflows, generic code editing, or non-Junior agent-skill authoring.

Skill与智能体开发
★ 411
getsentry
getsentry/junior

junior-qa

Validate Junior changes through local app-facing paths. Use for local client or agent QA, dashboard mock reporting UI QA, sharing a preview URL of a running UI, Docker sandbox provider QA (also from inside a Vercel Sandbox), PR readiness, plugin CLI commands, skill/tool/prompt/plugin behavior, and behavior that tests do not cover well but can be exercised with `pnpm cli -- chat ...`, another `pnpm cli` command, or `JUNIOR_DASHBOARD_MOCK_CONVERSATIONS=true pnpm dev`.

运维与部署Skill与智能体开发
★ 411
getsentry
getsentry/junior

eval-auth

Use for `/eval-auth` requests in MCP auth-resume integration tests. Always connect through the disclosed MCP tool before answering, then continue the user's actual request using prior thread context when needed.

Skill与智能体开发
★ 411
getsentry
getsentry/junior

jr-rpc

Manage low-level config and plugin introspection flows via jr-rpc bash commands. Use only when the user explicitly asks to read or update provider defaults/config or list installed plugins. Do not use for PR, branch, push, or auth-order questions; load the matching provider skill instead.

★ 411
getsentry
getsentry/junior

xdotcom

Read public X (Twitter) data through the read-only X API v2. Use when users share an x.com or twitter.com link, or ask what someone posted on X, what people are saying about a topic, product, or launch on X, how much chatter something got, or for a post's text, metrics, replies, or an account's recent posts. Do not use it to post, reply, like, repost, follow, or send DMs, or to read private or protected data.

★ 411
getsentry
getsentry/junior

vercel

Deploy and inspect Vercel apps, assign aliases, delete deployments, investigate logs, and monitor deployment outcomes. Use for Vercel deployment and log requests, not GitHub code changes or other cloud providers.

★ 411