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 34 stars 1 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 83/100

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

Skill Content

# Comment on a Linear Issue !`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: Render the preview Resolve the body: if `--body-file PATH` was given, read the file; otherwise take `--body TEXT` verbatim. If neither is present, STOP with `E_COMMENT_NO_BODY`. Show the resolved intent — the operation (`commentCreate`), the target issue, and the Markdown body — under: > **Proposed Linear write — review before sending** ## Step 3: 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 4: Send and render ``` accelerator linear comment add <IDENTIFIER> --body "..." ``` The subcommand emits a JSON envelope with a top-level `outcome` keyword. On `added`, confirm the comment was posted. On any non-...

Details

Author
atomicinnovation
Repository
atomicinnovation/accelerator
Created
6 months ago
Last Updated
yesterday
Language
Rust
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.

34 Updated yesterday
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.

34 Updated yesterday
atomicinnovation
Code & Development Listed

linear-issue-to-pr

Takes a Linear issue identifier (e.g. ENG-42) and carries it end to end in the current git repo - fetches the issue and its comments, creates or switches to the issue branch, implements the change, commits, pushes and opens a pull request (never merges). Use it whenever the user gives a Linear issue ID and wants it worked on, e.g. "get issue ENG-42", "work on ENG-42", "implement DBO-1104", "resuelve la issue ENG-42", "trabaja en ENG-42", or names a project together with an issue ID. Do not use it when the user only asks about an issue's status, wants to create or plan issues, or wants a summary without code changes.

1 Updated 3 days ago
mbarradev-debug