@sentry/junior-linear 0.73.0 → 0.74.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.
- package/package.json +1 -1
- package/skills/linear/SKILL.md +1 -1
package/package.json
CHANGED
package/skills/linear/SKILL.md
CHANGED
|
@@ -48,7 +48,7 @@ Classify the work as `bug`, `feature`, or `task`. Shape the title and body per [
|
|
|
48
48
|
- Do not add desired outcome, expected behavior, or acceptance criteria unless the thread explicitly requests them.
|
|
49
49
|
- 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.
|
|
50
50
|
|
|
51
|
-
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
|
|
51
|
+
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.
|
|
52
52
|
|
|
53
53
|
4. Set optional Linear fields literally:
|
|
54
54
|
|