Menu
Use when drafting, writing, or filing a Linear ticket/issue, or asked for a Linear title/body/description.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when drafting, writing, or opening a pull request (gh pr create), or asked for a PR title/body/description.
Writing voice for authored prose — PR bodies, Linear tickets, review comments, commit messages.
Hand a file to the user's running editor and block until they finish editing it. Use whenever a draft (PR body, ticket, commit message, any generated file) needs the user's review before you act on it, or when a task says "open this in my editor/vim/nvim".
Clojure style guidelines. Activate before writing or editing Clojure code
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design.
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
| name | linear-ticket |
| description | Use when drafting, writing, or filing a Linear ticket/issue, or asked for a Linear title/body/description. |
Voice: see the prose-voice skill.
/tmp/lin-<slug>.md) using the template below.remote-edit skill (blocking open).mcp__linear__save_issue (no id), mapping the front matter
below onto its parameters.---
# mcp__linear__save_issue fields — leave blank to omit. Title = first line below, body = rest.
team: # required — name or ID
project: # name, ID, or slug
assignee: # user ID, name, email, or "me"
labels: # name(s), comma-separated
priority: # 0 None, 1 Urgent, 2 High, 3 Medium, 4 Low
state: # workflow state type/name/ID
estimate: # number
cycle: # cycle name, number, or ID
milestone: # name or ID
parentId: # parent issue ID/identifier (e.g. LIN-123)
dueDate: # ISO date
---
Title goes on this line
Body prose (Markdown) goes here.
Map each non-empty front-matter key to its save_issue parameter (labels is a
list — split the comma-separated value; priority/estimate are numbers).
team is required on create. Title → title, content after it → description.