@sentry/junior-github 0.31.0 → 0.33.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sentry/junior-github",
-  "version": "0.31.0",
+  "version": "0.33.0",
   "private": false,
   "publishConfig": {
     "access": "public"

package/plugin.yaml

@@ -10,6 +10,7 @@ capabilities:
   - pull-requests.write
 
 config-keys:
+  - org
   - repo
 
 credentials:

package/skills/github-code/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: github-code
-description: Clone GitHub repositories, investigate source code, and manage pull requests via GitHub CLI. Use when users ask to inspect implementation details in a repository, clone code, edit files, answer source-code questions from repo evidence, or open/edit/view/merge pull requests. Prefer this skill for repository and code tasks even when the repo concerns Sentry products.
+description: Clone repositories, inspect source, edit code, and manage pull requests with GitHub CLI. Use for repo implementation questions, cloning/editing, PR inspection/mutation, and PR auth-order questions. For PR auth order, answer that `git push` needs GitHub remote write access before `gh pr create`. Prefer this skill for repository and code tasks even when the repo concerns Sentry products.
 allowed-tools: bash
 ---
 
@@ -21,6 +21,8 @@ Repository checkout, source-code investigation, and pull request operations via
 
 - Determine whether the task is `clone`, `source-code investigation`, a pull request inspection (`view`, `list`, `diff`, `checks`), or a pull request mutation (`create`, `update`, `close`, `merge`).
 - Resolve repository (`owner/repo`). If not explicit, query channel config with `jr-rpc config get github.repo` before running any `gh` or `git` command. If still missing, ask the user.
+- Run `jr-rpc config get github.repo` as its own bash command. Do not combine it with `cd`, `&&`, pipes, or any `gh` or `git` command.
+- After resolving a configured repo, pass it explicitly to the next `gh` command with `--repo owner/repo`; do not rely on implicit GitHub CLI repository discovery.
 - Resolve the pull request number for operations targeting an existing PR.
 - Keep `--repo owner/repo` explicit on `gh` commands so the command itself targets the intended repository, not a stale default.
 
@@ -46,6 +48,7 @@ Repository checkout, source-code investigation, and pull request operations via
 
 - Use for questions like "where is this implemented?", "how does this workflow work in code?", "is there already logic for X?", or "verify this from the repo."
 - If the current workspace already contains the target repository, inspect local files directly before cloning.
+- Do not treat this skill's `SKILL.md`, bundled references, or `/vercel/sandbox/skills/...` as target repository source code. If no checkout of the target repo is present, inspect the configured GitHub repository by cloning it shallowly or reading files through `gh` before answering.
 - Prefer the narrowest deterministic evidence: local file search, exact file reads, targeted clone inspection, existing issues/PRs, tests.
 - Cite repository evidence in the reply: file paths, symbols, issue/PR numbers, or commit references when known.
 - If evidence is incomplete, say what is unknown instead of guessing.
@@ -64,6 +67,7 @@ Repository checkout, source-code investigation, and pull request operations via
 
 #### 3. Resolve mutation inputs
 
+- For PR creation credential/order questions, explicitly answer that repository context comes first, then `git push` pushes the branch with GitHub remote write access, then `gh pr create` runs against the pushed branch with pull-request permissions.
 - For PR creation, resolve the base branch (explicit user request wins; otherwise repository default).
 - Resolve the head branch from the current checkout or user request.
 - If the head branch may not exist on the remote yet, push it explicitly before PR creation.

package/skills/github-code/references/api-surface.md

@@ -5,6 +5,7 @@ All operations use `gh` CLI. Commands must be deterministic and non-interactive.
 ## Repo scoping
 
 When the user omits `owner/repo`, resolve `github.repo` first with `jr-rpc config get github.repo`, then pass the resolved repo explicitly on the actual `gh` or `git` command.
+Run `jr-rpc config get github.repo` as a standalone bash command. Never chain it with `cd`, `&&`, pipes, or a provider command.
 Treat explicit repo flags as command-targeting safety rails, not as a credential-scoping mechanism.
 
 ## Capability to command mapping

package/skills/github-issues/SKILL.md

@@ -1,12 +1,13 @@
 ---
 name: github-issues
-description: Create, update, comment on, label, and inspect GitHub issues via GitHub CLI with concise, evidence-backed content. Use when users ask to open, edit, view, close, reopen, or triage GitHub issues — including tracking bugs, features, or tasks. Prefer this skill over generic repository tools for any issue operation.
+description: Create, update, comment on, label, and inspect GitHub issues via GitHub CLI with concise, evidence-backed content. Use when users ask to open, edit, view, close, reopen, or triage GitHub issues — including tracking bugs, features, or tasks. Prefer this skill over generic repository tools for issue operations; do not use for pull requests, branches, pushes, or PR auth-order questions.
 allowed-tools: bash
 ---
 
 # GitHub Issue Operations
 
 Issue create, update, comment, label, state, and inspection via `gh` CLI.
+Use only for GitHub issues. For pull requests, branches, pushes, or PR auth-order questions, load `github-code` instead.
 
 ## Reference loading
 
@@ -22,6 +23,8 @@ Issue create, update, comment, label, state, and inspection via `gh` CLI.
 
 - Determine whether the task is `create`, `update`, `comment`, `labels`, `state`, or read-only inspection.
 - Resolve repository (`owner/repo`). If not explicit, query channel config with `jr-rpc config get github.repo` before running any `gh` command. If still missing, ask the user.
+- Run `jr-rpc config get github.repo` as its own bash command. Do not combine it with `cd`, `&&`, pipes, or any `gh` command.
+- After resolving a configured repo, pass it explicitly to the next `gh` command with `--repo owner/repo`; do not rely on implicit GitHub CLI repository discovery.
 - Resolve the issue number for non-create operations.
 - Keep `--repo owner/repo` explicit on `gh` commands so the command itself targets the intended repository, not a stale default.
 
@@ -76,11 +79,13 @@ Run [references/issue-quality-checklist.md](references/issue-quality-checklist.m
 ### 5. Execute
 
 - Use `gh issue` commands from [references/api-surface.md](references/api-surface.md).
-- Check duplicates silently before creating a new issue.
+- For issue listing or other read-only inspection, prefer `--json` output so empty results still produce deterministic stdout.
+- Check duplicates silently before creating a new issue. Do not mention this check in the final reply unless a duplicate blocks creation.
 
 ### 6. Report result
 
-- Return canonical issue URL, issue number, issue type, and applied changes.
+- Return canonical issue URL, issue number, and issue type.
+- Mention only user-visible issue changes. Do not mention duplicate checks, searches, "no duplicates found", or routine preparation steps.
 
 ## Guardrails
 

package/skills/github-issues/references/api-surface.md

@@ -5,6 +5,7 @@ All operations use `gh` CLI. Commands must be deterministic and non-interactive.
 ## Repo scoping
 
 When the user omits `owner/repo`, resolve `github.repo` first with `jr-rpc config get github.repo`, then pass the resolved repo explicitly on the actual `gh` command.
+Run `jr-rpc config get github.repo` as a standalone bash command. Never chain it with `cd`, `&&`, pipes, or a `gh` command.
 Treat explicit repo flags as command-targeting safety rails, not as a credential-scoping mechanism.
 
 ## Capability to command mapping
@@ -25,6 +26,7 @@ Treat explicit repo flags as command-targeting safety rails, not as a credential
 | Add labels          | `gh issue edit NUMBER --repo owner/repo --add-label LABEL [--add-label LABEL2]`                               |
 | Remove labels       | `gh issue edit NUMBER --repo owner/repo --remove-label LABEL [--remove-label LABEL2]`                         |
 | Add comment         | `gh issue comment NUMBER --repo owner/repo --body-file PATH`                                                  |
+| List issues         | `gh issue list --repo owner/repo --json number,title,state,url --limit 20`                                    |
 | Read issue          | `gh issue view NUMBER --repo owner/repo --json number,title,state,labels,assignees,author,url,body`           |
 | Read comments       | `gh api /repos/owner/repo/issues/NUMBER/comments --method GET --header "Accept: application/vnd.github+json"` |