@sentry/junior-linear 0.30.0 → 0.32.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sentry/junior-linear",
-  "version": "0.30.0",
+  "version": "0.32.0",
   "private": false,
   "publishConfig": {
     "access": "public"

package/skills/linear/SKILL.md

@@ -1,12 +1,11 @@
 ---
 name: linear
 description: Manage Linear issues through Linear's hosted MCP server. Use when users ask to create a Linear ticket, update a Linear issue, add a Linear comment, move work between states, assign work, or look up Linear issue, team, or project details from Slack context.
-uses-config: linear.team linear.project
 ---
 
 # Linear Operations
 
-Use this skill for Linear issue workflows in the harness.
+Use this skill for Linear issue workflows.
 
 ## Reference loading
 
@@ -31,10 +30,8 @@ Load references conditionally based on the request:
 - If the request refers to an existing Linear item indirectly, inspect the current thread context for the previously mentioned issue key or URL before asking the user to restate it.
 - Ask one concise follow-up only when a write is blocked after considering both explicit user input and any configured defaults, such as multiple plausible teams, no clear target issue, or no valid team for a new issue.
 
-2. Discover and prepare MCP tools:
+2. Prepare the Linear operation:
 
-- `loadSkill` returns `available_tools` for this skill, including the exact `tool_name` values and input schemas exposed in this turn.
-- Call those exact tool names directly. Use `searchTools` only if you need to rediscover or filter the active Linear tools later in the turn.
 - Prefer a short read/search step before mutating when you need to confirm the existing issue, team, project, or workflow state.
 
 3. Draft issue content (create or substantial rewrite):
@@ -49,9 +46,9 @@ Classify the work as `bug`, `feature`, or `task`. Shape the title and body per [
 - Generalize session framing — strip channel references, slash commands, Slack thread IDs, user @mentions, and transcript fragments; replace with the underlying engineering problem.
 - Compress source material. Research notes, hypotheses, or transcripts become a short summary + scoped bullets — never paste raw investigation into the body.
 - Do not add desired outcome, expected behavior, or acceptance criteria unless the thread explicitly requests them.
-- When the request originated from a Slack thread or any on-behalf-of context, append a final line `Action taken on behalf of <name>.` using the user's real name.
+- When the request originated from a Slack thread or any on-behalf-of context, append a final line `Action taken on behalf of <name>.` using the action requester's real name. The action requester is the current `<requester>` or the person who explicitly asked you to create/update the issue, not necessarily the original reporter.
 
-Attribute the reporter by name when clear from the thread (e.g. "Raised by Alice during incident triage") — do not reference Slack channels, threads, or conversation metadata. Attach screenshots from the thread as image links when present. Preserve relevant URLs (Sentry, GitHub, docs, repro links) inline — do not dump a link list.
+Attribute the reporter by name when clear from the thread (e.g. "Raised by Alice during incident triage"). If the reporter differs from the action requester, keep them separate with durable body text such as `Reported by Alice.` — do not reference Slack channels, threads, or conversation metadata. Attach screenshots from the thread as image links when present. Preserve relevant URLs (Sentry, GitHub, docs, repro links) inline — do not dump a link list.
 
 4. Set optional Linear fields literally:
 
@@ -62,7 +59,7 @@ Attribute the reporter by name when clear from the thread (e.g. "Raised by Alice
 5. Verify draft before mutating:
 
 - Title length ≤ 60 characters.
-- Delegated-action footer is the last line when applicable.
+- Delegated-action footer is the last line when applicable, using the action requester's real name, not the reporter's name unless they are the same person.
 - No session framing remains (channel refs, slash commands, @mentions, Slack thread IDs).
 - Body structure matches complexity — no empty sections, no restated title, no raw research dump.
 

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

@@ -2,14 +2,6 @@
 
 Use this reference for any Linear operation.
 
-## Runtime contract
-
-- `loadSkill` returns `available_tools` for this skill, including the exact Linear MCP `tool_name` values exposed in the current turn.
-- Call those exact `tool_name` values directly.
-- Use `searchTools` only when you need to rediscover or filter the active Linear tools later in the same turn.
-- Do not hardcode raw Linear MCP tool names in advance. Tool discovery is part of the workflow.
-- Return the canonical Linear issue key or URL after successful writes.
-
 ## Provider capabilities
 
 Linear's hosted MCP server is intended for authenticated remote MCP access to Linear data.
@@ -26,49 +18,20 @@ The current public docs describe support for finding, creating, and updating obj
 
 ## Operation patterns
 
-| Intent               | Minimum tool pattern                                                                                             |
-| -------------------- | ---------------------------------------------------------------------------------------------------------------- |
-| Inspect an issue     | Resolve the issue by key, URL, or search query, then fetch current state before answering.                       |
+| Intent               | Minimum tool pattern                                                                                                         |
+| -------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
+| Inspect an issue     | Resolve the issue by key, URL, or search query, then fetch current state before answering.                                   |
 | Create an issue      | Confirm the team first, then create the issue with grounded title/body content and only the optional fields you can justify. |
-| Update fields        | Fetch current issue state first, then mutate only the requested fields.                                          |
-| Add a comment        | Resolve the exact issue first, then add a concise comment with durable links and next steps.                     |
-| Move state or assign | Read the current issue and team workflow first when state, workflow, or assignee ambiguity could cause the wrong mutation. |
-| Check for duplicates | Search for an existing matching issue before opening a new one when the request appears related to ongoing work. |
-
-## Config helpers
-
-Use these commands only when the user explicitly asks to inspect or store Linear defaults for the current conversation/channel.
-
-Resolve team default:
-
-```bash
-jr-rpc config get linear.team
-```
-
-Set team default:
-
-```bash
-jr-rpc config set linear.team Platform
-```
-
-Resolve project default:
-
-```bash
-jr-rpc config get linear.project
-```
-
-Set project default:
-
-```bash
-jr-rpc config set linear.project "Cross-team reliability"
-```
+| Update fields        | Fetch current issue state first, then mutate only the requested fields.                                                      |
+| Add a comment        | Resolve the exact issue first, then add a concise comment with durable links and next steps.                                 |
+| Move state or assign | Read the current issue and team workflow first when state, workflow, or assignee ambiguity could cause the wrong mutation.   |
+| Check for duplicates | Search for an existing matching issue before opening a new one when the request appears related to ongoing work.             |
 
 ## Content expectations
 
 - Translate Slack-thread wording into stable product or engineering language.
 - Preserve material links already present in the conversation, such as Sentry, GitHub, docs, repro, or dashboard URLs.
-- If the active MCP tool exposes structured link attachments, prefer those over burying important URLs only inside the prose body.
 - Keep provenance concise. Mention Slack origin only when it helps future readers understand why the issue exists.
-- Treat team, status, labels, estimate, cycle, and project as structured properties, not prose-only body content, when the MCP tool exposes them and the values are actually known.
+- Treat team, status, labels, estimate, cycle, and project as structured properties, not prose-only body content, when those fields are available and the values are actually known.
 - Prefer partial updates over full rewrites.
 - Label assumptions clearly when the thread leaves important details uncertain.

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

@@ -66,6 +66,4 @@ Use these patterns to shape concrete Linear requests.
 
 ## 11. When a user asks to set channel defaults for a Linear-heavy Slack thread
 
-- Use `jr-rpc config set linear.team <team name or key>` when the user explicitly asks to store a team default and the channel consistently routes new work to the same team.
-- Use `jr-rpc config set linear.project <project name>` when the user explicitly asks to store a project default and the channel mostly tracks one project.
 - Treat both defaults as optional. Explicit user input wins whenever a request names a different team or project.

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

@@ -65,6 +65,20 @@ Good body:
 >
 > Action taken on behalf of Carol.
 
+## Distinct reporter/requester
+
+Good body:
+
+> The reviewer bot resolved its own warning even though the underlying issue still appeared valid.
+>
+> Reported by Bojan Oro.
+>
+> - Original warning still applied after the thread was resolved
+> - The related PR remained blocked
+> - The bot should not resolve review threads without confirming the condition cleared
+>
+> Action taken on behalf of David Cramer.
+
 ## Anti-patterns
 
 - Adding "Expected behavior" or "Desired outcome" when the thread didn't state one
@@ -72,3 +86,4 @@ Good body:
 - Restating the title as the first sentence of the body
 - Including fix suggestions when the thread only describes the problem
 - Dumping a list of URLs without inline context
+- Conflating the reporter with the action requester when they differ

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

@@ -4,8 +4,6 @@ Use this reference when Linear MCP work fails or the request is ambiguous.
 
 | Symptom                                                   | Likely cause                                                                    | Response                                                                                                                                  |
 | --------------------------------------------------------- | ------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
-| No Linear tools are available after loading the skill     | The skill was not loaded or the provider tools were not activated for the turn  | Load the skill first and use the returned `available_tools`; use `searchTools` only if you need to rediscover them later in the turn.     |
-| Linear asks for authorization                             | The user has not connected Linear MCP access yet                                | Let the MCP OAuth flow pause and resume automatically; do not ask the user to paste credentials manually.                                 |
 | Authorization completes but the write still fails         | The connected Linear account lacks access to the target team, project, or issue | Retry only after confirming the target is visible to the user; otherwise explain the concrete access blocker.                             |
 | Creating a new issue is blocked                           | No team was resolved for the issue                                              | Ask for the team only when it is not already clear from the thread, project context, or existing issue references.                        |
 | Search returns too many matches                           | The request lacks a specific issue key, team, project, or title phrase          | Narrow the search with the most specific identifier present in the thread, then ask one concise follow-up only if ambiguity remains.      |