@sentry/junior-github 0.4.1 → 0.6.0

package/package.json

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

package/skills/github/README.md

@@ -57,6 +57,21 @@ Repeat for `preview` and `development` as needed. After env changes, redeploy so
 
 Run as a regular sandbox `bash` command while this skill is active:
 
+Clone a repository with a shallow checkout by default:
+
+```bash
+gh repo clone owner/repo -- --depth=1
+```
+
+Deepen later only if the task needs more history:
+
+```bash
+git -C repo fetch --depth=50 origin
+git -C repo fetch --unshallow
+```
+
+Issue operations still require scoped credentials:
+
 ```bash
 jr-rpc issue-credential github.issues.write
 gh issue create --repo owner/repo --title "Example issue" --body-file /vercel/sandbox/tmp/issue.md

package/skills/github/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: github
-description: Manage GitHub issue workflows via GitHub App identity with concise, evidence-backed content. Use when users ask to open, edit, label, comment on, close/reopen, or inspect GitHub issues via /github, especially when command-level CLI guidance is needed.
+description: Manage GitHub issue workflows and repository checkout via GitHub CLI with concise, evidence-backed content. Use when users ask to open, edit, label, comment on, close/reopen, or inspect GitHub issues via /github, or when they need `gh repo clone` guidance, especially shallow-clone defaults and exact CLI commands.
 requires-capabilities: github.issues.read github.issues.write github.issues.comment github.labels.write
 uses-config: github.repo
 allowed-tools: bash
@@ -8,19 +8,30 @@ allowed-tools: bash
 
 # GitHub Operations
 
-Use this skill for `/github` workflows in the harness. Issues are the primary supported surface today.
+Use this skill for `/github` workflows in the harness. Issues are the primary surface. Repository checkout is limited to `gh repo clone` guidance and execution when local code context is needed.
 
 ## Workflow
 
 1. Confirm operation and target:
-- Determine `create`, `update`, `comment`, `labels`, `state`, or read-only inspection.
-- Resolve repository (`owner/repo`) and issue number for non-create operations.
+- Determine `clone`, `create`, `update`, `comment`, `labels`, `state`, or read-only inspection.
+- Resolve repository (`owner/repo`) and issue number for non-create issue operations.
 - If repository is not explicit in args, query channel config:
   - `jr-rpc config get github.repo`
 - If config exists and is valid `owner/repo`, use it as default.
 - If repository is still missing, ask the user for `owner/repo`.
 
-2. Classify issue type before drafting:
+2. Handle repository checkout first when operation is `clone`:
+- Default to a shallow clone for local inspection or one-off edits:
+  - `gh repo clone owner/repo [directory] -- --depth=1`
+- Pass extra `git clone` flags only after `--`.
+- Use a full-history clone only when the task explicitly needs history-heavy operations such as `git blame`, `git bisect`, tag/release archaeology, or broad commit-log analysis.
+- If the initial shallow clone is insufficient, deepen incrementally instead of recloning:
+  - `git -C <directory> fetch --depth=<n> origin`
+  - `git -C <directory> fetch --unshallow`
+- When cloning a fork, keep the default upstream remote behavior unless the user asks for a different remote name.
+- After checkout, report the local directory and whether the clone is shallow or full. Stop here for clone-only requests.
+
+3. Classify issue type before drafting:
 - Use explicit user type when provided (`bug`, `feature`, `task`).
 - Otherwise infer from intent:
   - `bug`: broken behavior, regression, error, failure.
@@ -28,7 +39,7 @@ Use this skill for `/github` workflows in the harness. Issues are the primary su
   - `task`: maintenance, cleanup, docs, refactor, operational chore.
 - Default to `task` when uncertain.
 
-3. Draft issue content:
+4. Draft issue content:
 - Load the type-specific template:
   - `bug`: [references/issue-template-bug.md](references/issue-template-bug.md)
   - `feature`: [references/issue-template-feature.md](references/issue-template-feature.md)
@@ -42,29 +53,34 @@ Use this skill for `/github` workflows in the harness. Issues are the primary su
 - Cross-reference related issues and PRs when they provide context.
 - For quality gates, use [references/issue-quality-checklist.md](references/issue-quality-checklist.md).
 - For structure examples, use [references/issue-examples.md](references/issue-examples.md).
+- When creating a new issue on behalf of a user, append a final attribution line at the end of the body in the form `Action taken on behalf of <name>.`
+- Use the clearest available user identifier from conversation context. Prefer a human name, then stable handle, and do not omit attribution for delegated mutations.
 
-4. Execute operation:
+5. Execute operation:
 - Issue credential for the required capability before API calls:
   - Read-only (`gh issue view`, comment reads via `gh api`): `jr-rpc issue-credential github.issues.read`
   - Create/update/state changes: `jr-rpc issue-credential github.issues.write`
   - Comments: `jr-rpc issue-credential github.issues.comment`
   - Labels: `jr-rpc issue-credential github.labels.write`
+- Repository checkout does not need an issue credential step. Use `gh repo clone` directly.
 - Resolve command and flags from [references/api-surface.md](references/api-surface.md).
 - Execute using `gh` CLI directly. Use [references/github-issue-api.md](references/github-issue-api.md) for exact command shapes.
 - Use [references/common-use-cases.md](references/common-use-cases.md) for ready-to-run operation patterns.
 - If an operation fails, follow [references/troubleshooting-workarounds.md](references/troubleshooting-workarounds.md) before retrying.
 - Read [references/sandbox-runtime.md](references/sandbox-runtime.md) for credential delivery details.
 
-5. Report result:
-- Return canonical issue URL, issue number, issue type, applied changes, and confidence.
+6. Report result:
+- Return canonical issue URL, issue number, issue type, applied changes, and confidence for issue workflows.
+- For clone operations, return the repository, local directory, clone mode (`shallow` or `full`), and any follow-up deepen/unshallow action taken.
 - Include references used for verified claims.
 
 ## Guardrails
 
 - Execute operations as soon as required fields are available. Do not pause for confirmation unless the user explicitly asks for preview/dry-run.
 - Require explicit confirmation only for close/reopen or destructive broad rewrites.
+- Default to shallow clones for efficiency. Do not use a full clone unless the task requires repository history or the user asks for it.
 - Never claim verification without citing sources.
 - For `bug` issues, do not present a fix as definitive unless root-cause evidence is explicit.
 - Do not overwrite issue fields unless explicitly requested. Prefer partial updates over full body replacement.
 - If repository or installation access is missing, stop and return a concrete remediation message.
-- Scope is issue workflows only. Do not execute pull-request or repository admin mutations in this skill.
+- Scope is issue workflows plus repository checkout. Do not execute pull-request or repository admin mutations in this skill.

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

@@ -1,6 +1,6 @@
-# GitHub Issue CLI API Surface
+# GitHub CLI API Surface
 
-This skill supports issue workflows only.
+This skill supports issue workflows plus repository checkout via `gh repo clone`.
 
 All operations use `gh` CLI.
 
@@ -8,6 +8,7 @@ All operations use `gh` CLI.
 
 | Capability | Commands |
 | --- | --- |
+| none required | `gh repo clone` |
 | `github.issues.read` | `gh issue view`, `gh api /repos/.../comments` |
 | `github.issues.write` | `gh issue create`, `gh issue edit`, `gh issue close`, `gh issue reopen` |
 | `github.issues.comment` | `gh issue comment` |
@@ -17,6 +18,9 @@ All operations use `gh` CLI.
 
 | Operation | Command |
 | --- | --- |
+| Clone repository (default shallow) | `gh repo clone owner/repo [DIRECTORY] -- --depth=1` |
+| Deepen shallow clone | `git -C DIRECTORY fetch --depth=N origin` |
+| Convert shallow clone to full | `git -C DIRECTORY fetch --unshallow` |
 | Create issue | `gh issue create --repo owner/repo --title "..." [--body-file PATH]` |
 | Update issue fields | `gh issue edit NUMBER --repo owner/repo [--title "..."] [--body-file PATH]` |
 | Close issue | `gh issue close NUMBER --repo owner/repo [--comment "..."]` |
@@ -41,6 +45,12 @@ Set repo default:
 jr-rpc config set github.repo owner/repo
 ```
 
+Pass extra `git clone` flags after `--`:
+
+```bash
+gh repo clone owner/repo -- --depth=1 --filter=blob:none
+```
+
 Issue scoped credentials:
 
 ```bash

package/skills/github/references/common-use-cases.md

@@ -1,22 +1,54 @@
-# Common GitHub Issue CLI Use Cases
+# Common GitHub CLI Use Cases
 
 Use these patterns as direct execution playbooks.
 
-## 1) Create a bug issue
+## 1) Clone a repository for local work
+
+Default to a shallow clone unless the task requires full history:
+
+```bash
+gh repo clone owner/repo -- --depth=1
+```
+
+Clone into a specific directory:
+
+```bash
+gh repo clone owner/repo worktree/repo -- --depth=1
+```
+
+## 2) Deepen a shallow clone only when needed
+
+```bash
+git -C worktree/repo fetch --depth=50 origin
+```
+
+Convert to a full clone:
+
+```bash
+git -C worktree/repo fetch --unshallow
+```
+
+## 3) Create a bug issue
 
 ```bash
 jr-rpc issue-credential github.issues.write
 gh issue create --repo owner/repo --title "OAuth token refresh fails in long-running thread" --body-file /vercel/sandbox/tmp/issue.md
 ```
 
-## 2) Patch issue title/body
+`/vercel/sandbox/tmp/issue.md` should end with:
+
+```md
+Action taken on behalf of Jane Doe.
+```
+
+## 4) Patch issue title/body
 
 ```bash
 jr-rpc issue-credential github.issues.write
 gh issue edit 123 --repo owner/repo --title "Clarify retry semantics for lock contention" --body-file /vercel/sandbox/tmp/revised-issue.md
 ```
 
-## 3) Close or reopen issue
+## 5) Close or reopen issue
 
 ```bash
 jr-rpc issue-credential github.issues.write
@@ -29,14 +61,14 @@ Reopen:
 gh issue reopen 123 --repo owner/repo
 ```
 
-## 4) Add implementation comment
+## 6) Add implementation comment
 
 ```bash
 jr-rpc issue-credential github.issues.comment
 gh issue comment 123 --repo owner/repo --body-file /vercel/sandbox/tmp/comment.md
 ```
 
-## 5) Apply triage labels
+## 7) Apply triage labels
 
 ```bash
 jr-rpc issue-credential github.labels.write
@@ -49,14 +81,14 @@ Remove labels:
 gh issue edit 123 --repo owner/repo --remove-label needs-triage
 ```
 
-## 6) Read issue details before mutation
+## 8) Read issue details before mutation
 
 ```bash
 jr-rpc issue-credential github.issues.read
 gh issue view 123 --repo owner/repo --json number,title,state,labels,assignees,author,url,body
 ```
 
-## 7) Read comment history in JSON
+## 9) Read comment history in JSON
 
 ```bash
 jr-rpc issue-credential github.issues.read

package/skills/github/references/issue-examples.md

@@ -35,6 +35,8 @@ Good structure — problem-specific sections:
 >
 > ## Workaround
 > Retry wrapper that catches LockError and clears the dedup key (PR #32).
+>
+> Action taken on behalf of Jane Doe.
 
 ## Task example
 
@@ -52,6 +54,8 @@ Good scope — quantified and specific:
 > | `processReaction` | scheduling only |
 > | `processAction` | scheduling only |
 > | `processMessage` | scheduling + thread ID normalization + lock retry |
+>
+> Action taken on behalf of Jane Doe.
 
 ## Feature example
 
@@ -70,6 +74,8 @@ Good framing — current state, gap, options:
 > |----------|----------|
 > | File watch + hot reload | Simple, but no atomicity guarantee |
 > | Config service with polling | Consistent, but adds a dependency |
+>
+> Action taken on behalf of Jane Doe.
 
 ## Principles
 
@@ -86,3 +92,4 @@ Good framing — current state, gap, options:
 - Confident fix claims without root-cause evidence
 - Speculative detail mixed into verified facts
 - Session-specific content (user names, slash commands, channel references)
+- Missing delegated attribution footer on user-requested issue creation

package/skills/github/references/issue-template-bug.md

@@ -15,9 +15,15 @@ Up to 3 sentences describing the failure and its impact.
 
 Remove sections that don't apply. Add sections the problem needs.
 
+## Delegated action footer
+When creating a new issue on behalf of a user, append a final line:
+
+`Action taken on behalf of <name>.`
+
 ## Constraints
 - Title hard max: 60 characters (target 40-60).
 - Summary max 3 sentences.
 - Remove empty sections.
 - Adapt section headings to fit the issue, not the reverse.
 - Do not include acceptance criteria unless explicitly requested.
+- Keep the delegated action footer as the last line in the body when applicable to newly created issues.

package/skills/github/references/issue-template-feature.md

@@ -14,9 +14,15 @@ Up to 3 sentences describing the desired improvement and user outcome.
 
 Remove sections that don't apply. Add sections the feature needs.
 
+## Delegated action footer
+When creating a new issue on behalf of a user, append a final line:
+
+`Action taken on behalf of <name>.`
+
 ## Constraints
 - Title hard max: 60 characters (target 40-60).
 - Summary max 3 sentences.
 - Remove empty sections.
 - Adapt section headings to fit the issue, not the reverse.
 - Do not include acceptance criteria unless explicitly requested.
+- Keep the delegated action footer as the last line in the body when applicable to newly created issues.

package/skills/github/references/issue-template-task.md

@@ -14,9 +14,15 @@ Up to 3 sentences describing the task and intended result.
 
 Remove sections that don't apply. Add sections the task needs.
 
+## Delegated action footer
+When creating a new issue on behalf of a user, append a final line:
+
+`Action taken on behalf of <name>.`
+
 ## Constraints
 - Title hard max: 60 characters (target 40-60).
 - Summary max 3 sentences.
 - Remove empty sections.
 - Adapt section headings to fit the issue, not the reverse.
 - Do not include acceptance criteria unless explicitly requested.
+- Keep the delegated action footer as the last line in the body when applicable to newly created issues.

package/skills/github/references/troubleshooting-workarounds.md

@@ -1,15 +1,17 @@
-# GitHub Issue CLI Troubleshooting
+# GitHub CLI Troubleshooting
 
 Use this table to recover quickly while keeping operations deterministic.
 
 | Symptom | Likely cause | Fix |
 | --- | --- | --- |
 | `unknown command "issue"` from `gh` | CLI version too old or wrong binary. | Verify `gh --version`; ensure GitHub CLI from `gh-cli` repo is installed. |
+| `unknown flag: --depth` from `gh repo clone` | `git clone` flags were passed before `--`. | Pass clone flags after `--`, for example `gh repo clone owner/repo -- --depth=1`. |
 | `Missing required option --repo` | Repo not passed and no default was resolved. | Resolve with `jr-rpc config get github.repo`; pass `--repo owner/repo` explicitly when missing. |
 | `GraphQL: Could not resolve to a Repository` | Repo slug is wrong or inaccessible. | Validate `owner/repo` and confirm app installation on target repository. |
 | 401 Unauthorized | Credential not issued for current command scope. | Run `jr-rpc issue-credential <capability>` for the exact command and retry once. |
 | 403 Forbidden | App lacks required permission on repo. | Confirm GitHub App permissions and installation scope. |
 | 404 Not Found | Issue number or repo is wrong. | Validate repo + issue ID with `gh issue view NUMBER --repo owner/repo`. |
+| `git blame`, long log history, or old commits are missing after clone | Repo was cloned shallow by design. | Deepen incrementally with `git -C DIRECTORY fetch --depth=N origin`, or use `git -C DIRECTORY fetch --unshallow` when full history is required. |
 | `sandbox setup failed (dnf install gh failed ...)` | `gh` package not available in default repos. | Configure/install from GitHub RPM repo (`gh-cli`) in sandbox dependency bootstrap, then retry. |
 | `gh issue edit` does not change labels | Wrong flag usage or missing label capability context. | Use repeated `--add-label/--remove-label` flags and issue `github.labels.write` credential first. |
 | Comment command fails with empty body | Body file missing/empty. | Ensure comment file exists and has content before `gh issue comment`. |