Workflow origin for the Linear issue comment closure loop. It reads one Linear issue and current comments for context, creates exactly one owner-provided Markdown comment through recued-core.linear.comment.create, and when the comment succeeds it seeds durable data.shared closure state for linear-issue-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create, update, move, cancel, complete, delete, archive, assign, label, subscribe to, or otherwise mutate Linear issues.
Comment on Linear issue with closure watch
Workflow origin for the Linear issue comment closure loop. It reads one Linear issue and current comments for context, creates exactly one owner-provided Markdown comment through recued-core.linear.comment.create, and when the comment succeeds it seeds durable data.shared closure state for linear-issue-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create, update, move, cancel, complete, delete, archive, assign, label, subscribe to, or otherwise mutate Linear issues.
Complete workflow
Linear Issue Comment Closure Loop
4 pinned recipes
Workflow pack for Recued-created Linear issue comments. It composes the Linear capability pack with a closure ledger: add one owner-approved Markdown comment to an existing Linear issue, persist only the connection/issue/comment linkage in data.shared, and let a scheduled watcher re-read that exact issue until Linear reports it completed or canceled. This pack does not replace Linear comments, native notifications, issue workflow states, project views, reminders, roadmaps, or general issue reporting; it adds Recued-visible closure state for issue comments Recued created.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Scheduled adopter for Linear issue comment closure rows seeded by comment-linear-issue-with-closure. It lists only Recued-originated issue-comment watches, re-reads a bounded batch of Linear issue, and closes the shared row when Linear reports the issue completed or canceled. It can notify the owner on terminal issue state, but it never creates, updates, moves, cancels, completes, deletes, archives, assigns, labels, subscribes to, comments on, or otherwise mutates Linear issues.
Low-frequency timeout role for recued-core/linear-issue-comment-closure. It moves a bounded batch of expired rows from active to timed_out, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.
Owner-visible list/close role for recued-core/linear-issue-comment-closure. It lists bounded active, timed-out, and closed rows. Supplying a timed-out or closed key deletes only that exact terminal row; active watches cannot be deleted here.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (38 steps)
issue_id_value
trim
Trim whitespace from setting issue id
comment_body_value
trim
Trim whitespace from setting comment body
has_connection
compare
Check if setting linear has data
has_issue_id
compare
Check if issue id value has data
has_comment_body
compare
Check if comment body value has data
skip_issue_read
any
Check if any of the conditions are true
issue
?
skip: step.skip_issue_read equal true
live_issue_id
default
Apply default
has_live_issue_id
compare
Check if live issue id has data
skip_comment_context
any
Check if any of the conditions are true
comments_raw
?
skip: step.skip_comment_context equal true
state_type
default
Apply default
issue_already_completed
compare
Check if state type equals completed
issue_already_canceled
compare
Check if state type equals canceled
issue_terminal_before_comment
any
Check if any of the conditions are true
comments
default
Apply default
comment_count_before_create
count
Count items in comments
skip_comment_create
any
Check if any of the conditions are true
created_comment
?
skip: step.skip_comment_create equal true
created_comment_id_primary
default
Apply default
created_comment_id
default
Apply default
has_created_comment
compare
Check if created comment id has data
created_at
date_add
Add 0 days to
raw_issue_key
join
Join items with ":"
issue_key_colon
replace
Replace text in raw issue key
issue_key_slash
replace
Replace text in issue key colon
issue_key_dot
replace
Replace text in issue key slash
issue_key_at
replace
Replace text in issue key dot
issue_key_space
replace
Replace text in issue key at
issue_key_left_angle
replace
Replace text in issue key space
issue_key_right_angle
replace
Replace text in issue key left angle
issue_key_plus
replace
Replace text in issue key right angle
issue_key_equals
replace
Replace text in issue key plus
issue_key_question
replace
Replace text in issue key equals
skip_closure_seed
any
Check if any of the conditions are true
closure_timeout_at
date_add
Add setting no response timeout days days to
seed_linear_issue_comment_closure_watch
?
skip: step.skip_closure_seed equal true
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
linear
setting
=
issue id
setting
=
comment body
setting
=
no response timeout days
setting
=
30
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.