Skip to content
Recued
Menu
← Back to packs

GitHub Issue Comment Closure Loop

by recued-core v1 app_pack

Workflow pack for Recued-created GitHub issue comments. It composes the GitHub capability pack with a closure ledger: add one owner-approved Markdown comment to an existing GitHub issue, persist only the connection/repository/issue/comment linkage in data.shared, and let a scheduled watcher re-read that exact issue until GitHub reports it closed. This pack does not replace GitHub issue comments, native notifications, issue state controls, project boards, milestones, webhooks, or general issue reporting; it adds Recued-visible closure state for issue comments Recued created.

What this pack installs

Included recipes 4 pinned recipes

This pack installs the complete recipe workflow together. 2 supporting recipes run as background automation.

Workflow origin for the GitHub issue comment closure loop. It reads one GitHub issue and current comments for context, creates exactly one owner-provided Markdown comment through recued-core.github-pack.issue.comment, and when the comment succeeds it seeds durable data.shared closure state for github-issue-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create, update, close, reopen, delete, transfer, label, assign, lock, or otherwise mutate GitHub issues. It skips pull-request-shaped issue reads so code review remains on GitHub's pull request surfaces.

githubissuescommentsdeveloper-workflow
by recued-core pinned v1
GitHub issue comment closure watcher
Background automation

Scheduled adopter for GitHub issue comment closure rows seeded by comment-github-issue-with-closure. It lists only Recued-originated issue-comment watches, re-reads a bounded batch of GitHub issue, and closes the shared row when GitHub reports that issue closed. It can notify the owner on closure, but it never creates, updates, closes, reopens, deletes, transfers, labels, assigns, locks, comments on, or otherwise mutates GitHub issues.

githubissuescommentsdeveloper-workflow
by recued-core pinned v1

Low-frequency timeout role for recued-core/github-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.

githubwatchertimeoutowner-review
by recued-core pinned v1

Owner-visible list/close role for recued-core/github-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.

githubwatcherreviewclose
by recued-core pinned v1

Builds on

Trust & control

What installing this whole pack would let it do. Recued grants these permissions at install — review them there before approving.

Where it runs

Device + server Runs on your device (browser) or your server.

Data it touches

Warehousedata.shared

About

Tags

pack:github-issue-comment-closuregithubissuescommentsdeveloper-workflowclosureclosed-loopstate:github-issue-comment-closure-watcherworkflowsoloone-person-companyv3