comment-linear-issue

Solid

Use this skill only when the user explicitly invokes /comment-linear-issue to add a Markdown comment to an existing Linear issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. It shows the comment preview, requires explicit confirmation, then posts the comment.

Code & Development 30 stars 1 forks Updated today MIT

Install

View on GitHub

Quality Score: 85/100

Stars 20%
50
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
83
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Comment on a Linear Issue !`${CLAUDE_PLUGIN_ROOT}/bin/accelerator config context --skill comment-linear-issue --fail-safe` > **Configuration**: Set `work.integration: linear` in `.accelerator/config.md`. Add a Markdown comment to a Linear issue via `commentCreate`. Work through the steps in order. This skill never auto-invokes — it only runs when the user explicitly types `/comment-linear-issue`. The comment body comes ONLY from text the user typed this turn or a file path the user named this turn — never synthesised from prior context. ## Step 1: Parse arguments Read the issue identifier (positional) and the body source (`--body TEXT` or `--body-file PATH`). ## Step 2: Generate the preview ``` ${CLAUDE_PLUGIN_ROOT}/skills/integrations/linear/scripts/linear-comment-flow.sh \ <IDENTIFIER> --body "..." --print-payload ``` If the helper exits non-zero (e.g. no body — `E_COMMENT_NO_BODY`), STOP and report the error. ## Step 3: Render the preview Show the operation (`commentCreate`), the target issue, and the Markdown body under: > **Proposed Linear write — review before sending** ## Step 4: Confirm before writing Ask: > Post this comment to Linear? Reply **y** to confirm, **n** to revise, anything > else to abort. On a clear yes, proceed. On no/revise, rebuild the preview. On anything ambiguous, abort with "Aborted — no Linear write was made." ## Step 5: Send and render ``` ${CLAUDE_PLUGIN_ROOT}/skills/integrations/linear/scripts/linear-comment-flow.sh \ <...

Details

Author
atomicinnovation
Repository
atomicinnovation/accelerator
Created
5 months ago
Last Updated
today
Language
HTML
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

create-linear-issue

Use this skill only when the user explicitly invokes /create-linear-issue to create a new Linear issue from a local work-item file. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. It reads the work item's title and Markdown body, shows a payload preview, requires explicit confirmation, then creates the issue and writes the remote-allocated identifier (e.g. BLA-123) back into the file's external_id frontmatter field.

30 Updated today
atomicinnovation
Code & Development Solid

update-linear-issue

Use this skill only when the user explicitly invokes /update-linear-issue to change fields on an existing Linear issue (title, description, state, assignee, priority). This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. It shows a payload preview, requires explicit confirmation, then applies the update.

30 Updated today
atomicinnovation
Code & Development Solid

comment-jira-issue

Use this skill only when the user explicitly invokes /comment-jira-issue to add, list, edit, or delete comments on a Jira issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. Subcommands: add (post a new comment), list (fetch all comments with pagination), edit (update an existing comment), delete (remove a comment — irreversible). Write subcommands show a payload preview and require explicit confirmation before calling the API.

30 Updated today
atomicinnovation