@sentry/junior-sentry 0.20.0 → 0.21.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/package.json +1 -1
  2. package/plugin.yaml +1 -1
  3. package/skills/sentry/SKILL.md +6 -2
  4. package/skills/sentry/references/cli-commands.md +2 -16
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sentry/junior-sentry",
3
- "version": "0.20.0",
3
+ "version": "0.21.1",
4
4
  "private": false,
5
5
  "publishConfig": {
6
6
  "access": "public"
package/plugin.yaml CHANGED
@@ -22,7 +22,7 @@ oauth:
22
22
  client-secret-env: SENTRY_CLIENT_SECRET
23
23
  authorize-endpoint: https://sentry.io/oauth/authorize/
24
24
  token-endpoint: https://sentry.io/oauth/token/
25
- scope: "event:read org:read project:read"
25
+ scope: "event:read org:read project:read team:read"
26
26
 
27
27
  runtime-dependencies:
28
28
  - type: npm
package/skills/sentry/SKILL.md CHANGED
@@ -14,7 +14,7 @@ Use this skill for Sentry investigation workflows in the harness.
14
14
 
15
15
  1. Confirm operation and target:
16
16
 
17
- - Determine operation: `issue list`, `issue explain`, `issue plan`, `replays`, `deep-link`, or general query.
17
+ - Determine operation: `issue list`, `deep-link`, or general query.
18
18
  - Resolve org from channel config: `jr-rpc config get sentry.org`
19
19
  - Resolve project from channel config: `jr-rpc config get sentry.project` (optional — many queries span multiple projects).
20
20
  - If org is missing and needed, ask the user.
@@ -25,7 +25,10 @@ Use this skill for Sentry investigation workflows in the harness.
25
25
  - The CLI reads `SENTRY_AUTH_TOKEN` from env after the runtime enables the declared Sentry capability for this turn.
26
26
  - Read [references/cli-commands.md](references/cli-commands.md) for command shapes and flags.
27
27
  - Read [references/sandbox-runtime.md](references/sandbox-runtime.md) before relying on sandbox credentials.
28
- - If a Sentry API call returns 401 or 403 after credentials were issued, the user's token may lack access for the requested org. Run `jr-rpc delete-token sentry` to clear the stale token, then retry after re-enabling the declared capability. Do not ask the user to run a command manually — the system handles re-authorization automatically.
28
+ - If a Sentry API call returns `401`, or clearly says the token is invalid, expired, revoked, or unauthorized, run `jr-rpc delete-token sentry` to clear the stale token, then retry after re-enabling the declared capability.
29
+ - If a Sentry API call explicitly says `missing scope`, `missing scopes`, or `insufficient scope`, run `jr-rpc delete-token sentry` to clear the outdated grant, then retry after re-enabling the declared capability.
30
+ - If a Sentry API call returns a generic `403`, `permission denied`, or otherwise indicates missing org/project access without naming missing scopes, stop and tell the user the current Sentry connection could not access the requested Sentry data.
31
+ - Only mention a specific missing scope when the CLI or API error explicitly names that scope. Do not guess scope names from a generic `403`.
29
32
 
30
33
  3. Generate deep links:
31
34
 
@@ -40,6 +43,7 @@ Use this skill for Sentry investigation workflows in the harness.
40
43
  ## Guardrails
41
44
 
42
45
  - Read-only operations only (MVP scope).
46
+ - Avoid speculative or experimental Sentry CLI subcommands that are not listed in the bundled references.
43
47
  - Do not print credential values.
44
48
  - If org is missing and needed, ask the user.
45
49
  - Prefer deep links over raw data dumps when linking to Sentry web UI.
package/skills/sentry/references/cli-commands.md CHANGED
@@ -15,22 +15,6 @@ sentry issues list --org ORG [--project PROJECT] [--query QUERY] [--json]
15
15
  - `--query`: Sentry search query (e.g., `user.email:alice@example.com`, `is:unresolved`).
16
16
  - `--json`: Output as JSON for structured parsing.
17
17
 
18
- ### Explain issue
19
-
20
- ```bash
21
- sentry issues explain ISSUE_ID --org ORG [--json]
22
- ```
23
-
24
- AI-powered root cause analysis for a specific issue.
25
-
26
- ### Plan fix
27
-
28
- ```bash
29
- sentry issues plan ISSUE_ID --org ORG [--json]
30
- ```
31
-
32
- AI-powered remediation guidance for a specific issue.
33
-
34
18
  ## Organization commands
35
19
 
36
20
  ### List organizations
@@ -47,3 +31,5 @@ Lists organizations accessible with current token.
47
31
  - `--org ORG`: Organization slug.
48
32
  - `--project PROJECT`: Project slug.
49
33
  - `--log-level`: `debug`, `info`, `warn`, `error`.
34
+
35
+ Only use commands listed in this reference during normal skill execution. If a command reports explicit missing scopes, reconnect the Sentry account to refresh the grant. Treat generic permission or org/project access errors as access problems rather than retryable auth refresh problems.