github-issue-task-updater

You can update a GitHub issue task by resolving the target issue via number or URL, reading its context and recent comments, synthesizing accepted changes into a revised specification, previewing edits, and writing the updated task definition back to the same issue.

Syncing GitHub issue acceptance criteria with reviewer feedback is supported by synthesizing accepted comment changes—such as clarifications or criteria revisions—into the existing planning issue while preserving original constraints and intent. Section-level edits are previewed before writeback.

The best way to rewrite a GitHub planning issue after discussion is to resolve the issue by an active planning marker, read recent comments, and synthesize accepted decisions into a revised task specification. It preserves constraints and verifies writeback to the same issue.

Manual editing is unnecessary when PR comments propose scope changes. This Skill applies to PR-linked task updates by resolving identifiers, reading issue context, synthesizing accepted comment changes, previewing edits, and writing updates back while preserving the original task constraints.

Original constraints are preserved when applying comment revisions. The Skill synthesizes accepted changes from comments into a revised task specification while explicitly preserving the original intent, constraints, and acceptance criteria before writing updates back to the issue.

You should not use an automated workflow to amend GitHub issue tasks when comments are unresolved or rejected, as the Skill synthesizes only accepted changes and confirmed decisions into the revised specification to keep the canonical task accurate and actionable.