@sentry/junior-linear 0.90.0 → 0.92.0

package/package.json

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

package/skills/linear/SKILL.md

@@ -46,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 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.
+- 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 actor's real name. The action actor is the current `<actor>` 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"). 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 internals. 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 actor, keep them separate with durable body text such as `Reported by Alice.` — do not reference Slack channels, threads, or conversation internals. 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:
 
@@ -59,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, using the action requester's real name, not the reporter's name unless they are the same person.
+- Delegated-action footer is the last line when applicable, using the action actor'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/issue-examples.md

@@ -65,7 +65,7 @@ Good body:
 >
 > Action taken on behalf of Carol.
 
-## Distinct reporter/requester
+## Distinct reporter/actor
 
 Good body:
 
@@ -86,4 +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
+- Conflating the reporter with the action actor when they differ