thread-magic/super-magic-skills/linear-release-notes

Claude Code and agent skill by thread-magic/super-magic-skills

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Turn a completed Linear cycle's issues into client-safe release notes and post fix notices to affected tickets. Close the loop on shipped bugs.

Install

npx vskill@latest install thread-magic/super-magic-skills/linear-release-notes

SKILL.md

The same SKILL.md was published earlier as thread-magic/super-magic-skills/linear-release-notes.

Linear Release Notes

When to use: "Cycle just ended — draft the release notes," or "the <symptom> bug shipped; notify all the tickets waiting on it."

Run it: across all tickets waiting on the shipped issues (run manually after a cycle closes).

Prompt

Close the loop MSPs usually drop: engineering ships the fix, but the clients who reported it
never hear. Convert a completed Linear cycle into plain-language release notes and deliver the
"your issue is fixed" message to every waiting ticket.
This needs the member's connected Linear, scoped to their workspace access. If Linear isn't
connected, degrade by drafting the release notes from a pasted issue list — do not stop.
1. Pull the completed cycle in Linear and its issues in a done state. Exclude non-shipped states
(canceled, duplicate). Never treat "in review" as shipped.
2. For each shipped issue, read it (and its comments where the user-visible effect is unclear)
and translate to a client-safe line: what the user experienced → what is now fixed, in plain
language. Strip internal jargon, code details, blame, and anything security-sensitive (a fixed
vulnerability is "a security improvement", never with exploit detail).
3. Assemble the notes: Fixed / Improved / Known issues sections, dated. Show me the draft for
review — nothing external moves before you approve the wording.
4. Map issues to waiting tickets: search tickets referencing each issue id or tracked as waiting
on it. Present the ticket list per issue for confirmation — this is the blast radius; a
wrong-ticket fix notice tells a client their unfixed problem is solved.
5. On confirmation, for each affected ticket: leave a note with the relevant fix notice only
(plain text, no markdown — PSA-safe; not the whole release notes), and propose the "fix shipped
— verify with client" status where the member wants it. Ticket notes are plain text; ask
whether the note is internal or client-visible, don't assume.
6. Report: notes published (where the member chose to put them), tickets noted, tickets skipped
and why.

Security

  • Security scanPassed, 95 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
3
Repository forks
3
7-day trend score
12

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/thread-magic/super-magic-skills/linear-release-notes/badge)](https://verified-skill.com/skills/thread-magic/super-magic-skills/linear-release-notes)

Something wrong with this skill or its page? Tell us.