github-issue-task-updater

Update GitHub issue task definitions from accepted discussion comments.

Updated Aug 23, 2026

Search Tags:#automation #workflow #github #comments #issue #amend #task

Ready to run

npx skills add https://github.com/ai212983/gh-csi --skill github-issue-task-updater

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-issue-task-updater
Source: https://github.com/ai212983/gh-csi/tree/main/skills/github-issue-task-updater
Command: npx skills add https://github.com/ai212983/gh-csi --skill github-issue-task-updater

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many GitHub issues drift away from the agreed task definition during review and discussion, leaving acceptance criteria and scope inconsistent with reviewer feedback. This Skill streamlines updating an existing issue to reflect accepted comments and decisions so the canonical task stays accurate and actionable.

Core Features & Use Cases

Resolve the target issue by explicit number, URL, or an active planning marker and read the current issue context and recent comments.
Synthesize accepted changes from comments into a revised task specification while preserving intent, constraints, and acceptance criteria.
Preview section-level edits for confirmation, apply updates to the same issue when approved or when the user issues an explicit imperative, and verify the writeback.

Quick Start

Update issue #123 to incorporate accepted review comments and persist the revised task definition back to the same issue.

Frequently Asked Questions about github-issue-task-updater

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I update GitHub issue tasks from discussion comments?▼

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.

Can I sync GitHub issue acceptance criteria with reviewer feedback automatically?▼

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.

What is the best way to rewrite a GitHub planning issue after a long discussion thread?▼

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.

Do I need to manually edit GitHub issues when PR comments propose scope changes?▼

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.

Does this issue task updater preserve original constraints when applying comment revisions?▼

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.

When should I not use an automated workflow to amend GitHub issue tasks?▼

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.