@sentry/junior-sentry 0.74.1 → 0.75.0

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/skills/sentry/SKILL.md +2 -2
  3. package/skills/sentry/SOURCES.md +32 -28
  4. package/skills/sentry/SPEC.md +2 -1
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sentry/junior-sentry",
3
- "version": "0.74.1",
3
+ "version": "0.75.0",
4
4
  "private": false,
5
5
  "publishConfig": {
6
6
  "access": "public"
package/skills/sentry/SKILL.md CHANGED
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: sentry
3
- description: Query live Sentry telemetry with the Sentry CLI and generate Sentry deep links. Use when users ask to investigate Sentry issues, events, logs, traces, organizations, projects, replays, or authenticated Sentry API data. Do not use it for repository/source-code/PR tasks, even when the topic concerns Sentry products.
3
+ description: Query live Sentry telemetry with the Sentry CLI and generate Sentry deep links. Use when users ask to investigate Sentry issues, events, logs, traces, organizations, projects, replays, product feature usage, Sentry's own product telemetry, or authenticated Sentry API data. Do not use it for repository/source-code/PR tasks, even when the topic concerns Sentry products.
4
4
  allowed-tools: bash
5
5
  ---
6
6
 
@@ -18,7 +18,7 @@ Before declaring a Sentry data surface unavailable, verify the current CLI help:
18
18
 
19
19
  1. Confirm operation and target:
20
20
 
21
- - Determine operation: issue, event, log, trace, org, project, replay/deep-link, or API query.
21
+ - Determine operation: issue, event, log, trace, org, project, replay/deep-link, Sentry product feature usage, or API query.
22
22
  - Resolve org from channel config: `jr-rpc config get sentry.org`
23
23
  - Resolve project from channel config: `jr-rpc config get sentry.project` (optional — many queries span multiple projects).
24
24
  - If org is missing and needed, ask the user.
package/skills/sentry/SOURCES.md CHANGED
@@ -1,42 +1,45 @@
1
1
  # Sentry Skill Sources
2
2
 
3
- Last updated: 2026-04-30
3
+ Last updated: 2026-06-18
4
4
 
5
5
  ## Source inventory
6
6
 
7
- | Source | Trust tier | Confidence | Contribution | Usage constraints |
8
- | --------------------------------------------------------------- | ---------- | ---------- | --------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- |
9
- | `https://github.com/getsentry/junior/issues/271` | canonical | high | Regression report: Junior tried stale `sentry organizations list` and should verify current CLI help before blocking. | Use as issue context, not as a full command reference. |
10
- | `https://cli.sentry.dev/commands/issue/` | canonical | high | Current `sentry issue list`, target syntax, issue subcommands, and JSON support. | Verify live help when runtime CLI differs. |
11
- | `https://cli.sentry.dev/commands/org/` | canonical | high | Current `sentry org list` and `sentry org view` commands. | Verify live help when runtime CLI differs. |
12
- | `https://cli.sentry.dev/commands/log/` | canonical | high | Current `sentry log list` and `sentry log view` commands, trace filtering, and log query flags. | Verify live help when runtime CLI differs. |
13
- | `https://cli.sentry.dev/commands/trace/` | canonical | high | Current `sentry trace list`, `view`, and `logs` commands. | Verify live help when runtime CLI differs. |
14
- | `https://cli.sentry.dev/commands/api/` | canonical | high | Authenticated `sentry api <endpoint>` fallback and request flags. | Use read-only requests unless the user asks for mutation. |
15
- | `https://cli.sentry.dev/configuration/` | canonical | high | `SENTRY_AUTH_TOKEN`, JSON/global flags, cache controls, and runtime configuration behavior. | Junior injects credentials; do not persist or print tokens. |
16
- | `pnpm view sentry version dist-tags description bin repository` | canonical | high | Confirmed npm package `sentry` latest is `0.30.0` and exposes `sentry` binary. | Package metadata only; command behavior still comes from help/docs. |
17
- | `pnpm dlx sentry@latest --help` and subcommand help | canonical | high | Confirmed executable help lists org list/view, issue list/events/view, log list/view, trace list/view/logs, and api. | Re-run when updating for a newer CLI. |
18
- | `packages/junior-sentry/plugin.yaml` | canonical | high | Confirms runtime dependency is the npm `sentry` package and auth token env is `SENTRY_AUTH_TOKEN`. | Local repo contract. |
7
+ | Source | Trust tier | Confidence | Contribution | Usage constraints |
8
+ | --------------------------------------------------------------- | ---------- | ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- |
9
+ | `https://github.com/getsentry/junior/issues/271` | canonical | high | Regression report: Junior tried stale `sentry organizations list` and should verify current CLI help before blocking. | Use as issue context, not as a full command reference. |
10
+ | `https://cli.sentry.dev/commands/issue/` | canonical | high | Current `sentry issue list`, target syntax, issue subcommands, and JSON support. | Verify live help when runtime CLI differs. |
11
+ | `https://cli.sentry.dev/commands/org/` | canonical | high | Current `sentry org list` and `sentry org view` commands. | Verify live help when runtime CLI differs. |
12
+ | `https://cli.sentry.dev/commands/log/` | canonical | high | Current `sentry log list` and `sentry log view` commands, trace filtering, and log query flags. | Verify live help when runtime CLI differs. |
13
+ | `https://cli.sentry.dev/commands/trace/` | canonical | high | Current `sentry trace list`, `view`, and `logs` commands. | Verify live help when runtime CLI differs. |
14
+ | `https://cli.sentry.dev/commands/api/` | canonical | high | Authenticated `sentry api <endpoint>` fallback and request flags. | Use read-only requests unless the user asks for mutation. |
15
+ | `https://cli.sentry.dev/configuration/` | canonical | high | `SENTRY_AUTH_TOKEN`, JSON/global flags, cache controls, and runtime configuration behavior. | Junior injects credentials; do not persist or print tokens. |
16
+ | `pnpm view sentry version dist-tags description bin repository` | canonical | high | Confirmed npm package `sentry` latest is `0.30.0` and exposes `sentry` binary. | Package metadata only; command behavior still comes from help/docs. |
17
+ | `pnpm dlx sentry@latest --help` and subcommand help | canonical | high | Confirmed executable help lists org list/view, issue list/events/view, log list/view, trace list/view/logs, and api. | Re-run when updating for a newer CLI. |
18
+ | `packages/junior-sentry/plugin.yaml` | canonical | high | Confirms runtime dependency is the npm `sentry` package and auth token env is `SENTRY_AUTH_TOKEN`. | Local repo contract. |
19
+ | `https://github.com/getsentry/junior/issues/615` | canonical | high | Regression report: Sentry product feature usage routed to Hex, then an explicit "use Sentry telemetry" redirect was ignored after Hex auth paused. | Use as routing evidence, not as command reference. |
19
20
 
20
21
  ## Decisions
21
22
 
22
- | Decision | Status | Rationale |
23
- | ---------------------------------------------------------- | -------- | ------------------------------------------------------------------------------------------------------- |
24
- | Use singular canonical command groups in runtime guidance. | adopted | Current docs and latest executable help use `issue`, `org`, `log`, and `trace`. |
25
- | Add a live-help verification gate before blocking. | adopted | Issue 271 showed a stale remembered command produced a false blocked answer. |
26
- | Keep `sentry api <endpoint>` as a read-only fallback. | adopted | Current CLI exposes an authenticated API escape hatch for resources not covered by high-level commands. |
27
- | Prefer `--json` and optional `--fields` for parsing. | adopted | Current CLI supports machine-readable output across command groups. |
28
- | Preserve stale plural subcommands as recommended forms. | rejected | `organizations list` was the root failure; aliases should not be taught as canonical command shapes. |
29
- | Create a broad new troubleshooting reference. | deferred | Current failure modes fit in the focused CLI reference without crowding `SKILL.md`. |
23
+ | Decision | Status | Rationale |
24
+ | ---------------------------------------------------------------------------------------------------- | -------- | ------------------------------------------------------------------------------------------------------------- |
25
+ | Use singular canonical command groups in runtime guidance. | adopted | Current docs and latest executable help use `issue`, `org`, `log`, and `trace`. |
26
+ | Add a live-help verification gate before blocking. | adopted | Issue 271 showed a stale remembered command produced a false blocked answer. |
27
+ | Keep `sentry api <endpoint>` as a read-only fallback. | adopted | Current CLI exposes an authenticated API escape hatch for resources not covered by high-level commands. |
28
+ | Prefer `--json` and optional `--fields` for parsing. | adopted | Current CLI supports machine-readable output across command groups. |
29
+ | Treat Sentry product feature usage and explicit Sentry telemetry redirects as Sentry skill triggers. | adopted | Issue 615 showed the previous trigger language under-specified product-introspection queries and let Hex win. |
30
+ | Preserve stale plural subcommands as recommended forms. | rejected | `organizations list` was the root failure; aliases should not be taught as canonical command shapes. |
31
+ | Create a broad new troubleshooting reference. | deferred | Current failure modes fit in the focused CLI reference without crowding `SKILL.md`. |
30
32
 
31
33
  ## Coverage matrix
32
34
 
33
- | Dimension | Coverage status | Evidence |
34
- | ---------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
35
- | API surface and behavior contracts | complete | `cli-commands.md` covers issue, org, log, trace, and API command shapes plus live help verification. |
36
- | Config/runtime options | complete | `sandbox-runtime.md`, `plugin.yaml`, and CLI configuration docs cover injected auth and runtime package installation. |
37
- | Common use cases | complete | `cli-commands.md` maps org listing, issue search/view/events, logs, traces, trace logs, and API fallback. |
38
- | Known issues/workarounds | complete | `cli-commands.md` troubleshooting covers stale plural commands, target syntax, JSON parsing, cache, auth, scope, and access failures. |
39
- | Version/migration variance | complete | The skill now treats live CLI help as final when references and installed CLI disagree. |
35
+ | Dimension | Coverage status | Evidence |
36
+ | ---------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
37
+ | API surface and behavior contracts | complete | `cli-commands.md` covers issue, org, log, trace, and API command shapes plus live help verification. |
38
+ | Config/runtime options | complete | `sandbox-runtime.md`, `plugin.yaml`, and CLI configuration docs cover injected auth and runtime package installation. |
39
+ | Common use cases | complete | `cli-commands.md` maps org listing, issue search/view/events, logs, traces, trace logs, and API fallback. |
40
+ | Product telemetry routing | documented | `SKILL.md` and `SPEC.md` cover Sentry product feature usage and explicit "Sentry telemetry" redirects after an unrelated auth pause. A dedicated eval should wait for the eval harness boundary cleanup. |
41
+ | Known issues/workarounds | complete | `cli-commands.md` troubleshooting covers stale plural commands, target syntax, JSON parsing, cache, auth, scope, and access failures. |
42
+ | Version/migration variance | complete | The skill now treats live CLI help as final when references and installed CLI disagree. |
40
43
 
41
44
  ## Open gaps
42
45
 
@@ -44,4 +47,5 @@ Last updated: 2026-04-30
44
47
 
45
48
  ## Changelog
46
49
 
50
+ - 2026-06-18: Expanded trigger language for Sentry product telemetry and feature usage, and recorded issue 615 routing evidence.
47
51
  - 2026-04-30: Reconciled skill guidance with Sentry CLI `0.30.0`, replaced stale plural command forms, added live-help verification, expanded log/trace/API guidance, updated eval smoke artifacts, and added an org-list command-selection eval.
package/skills/sentry/SPEC.md CHANGED
@@ -10,6 +10,7 @@ It should produce useful read-only investigation results or Sentry web links wit
10
10
  In scope:
11
11
 
12
12
  - Listing and viewing Sentry issues, issue events, logs, traces, organizations, and related read-only data.
13
+ - Investigating Sentry's own product telemetry and product feature usage through Sentry CLI/API data surfaces.
13
14
  - Using `sentry api <endpoint>` for authenticated read-only requests when no high-level command exists.
14
15
  - Generating Sentry deep links for user-scoped or entity-specific views.
15
16
  - Diagnosing auth, scope, and access failures without guessing missing scopes.
@@ -23,7 +24,7 @@ Out of scope:
23
24
  ## Users And Trigger Context
24
25
 
25
26
  - Primary users: Junior users asking Slack or harness agents to investigate Sentry data.
26
- - Common user requests: "list my Sentry issues", "show error logs", "inspect this trace", "which orgs can I access", "open the issue in Sentry".
27
+ - Common user requests: "list my Sentry issues", "show error logs", "inspect this trace", "which orgs can I access", "open the issue in Sentry", "use Sentry telemetry", and "how much is this Sentry feature used".
27
28
  - Should not trigger for: source-code tasks, GitHub PRs, repository searches, or generic questions about Sentry SDK implementation.
28
29
 
29
30
  ## Runtime Contract