issue-status-sync

Name: issue-status-sync
Availability: InStock
Author: burburton

Post execution progress comments to GitHub Issues without closing them.

Updated Mar 22, 2026

Search Tags:#documentation #commenting #acceptance #github-issues #artifact-reading #issue-status-sync

Ready to run

npx skills add https://github.com/Burburton/amazing_agent_specialist --skill issue-status-sync-burburton

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issue-status-sync
Source: https://github.com/Burburton/amazing_agent_specialist/tree/main/.opencode/skills/docs/issue-status-sync
Command: npx skills add https://github.com/Burburton/amazing_agent_specialist --skill issue-status-sync-burburton

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents premature closure of GitHub Issues by posting deterministic progress updates from the execution layer while keeping the Issue open for final acceptance.

Core Features & Use Cases

Post execution progress as a documentation-like comment on the related Issue without altering its state.
Consume upstream artifacts (acceptance decisions, verification results, etc.) to build a traceable progress narrative.
Generate a DOC-003 compliant progress report and a styled GitHub comment using a standard template for management review.

Quick Start

After an execution run completes, trigger this skill to post a progress comment on the corresponding GitHub Issue and keep it OPEN for acceptance.

Frequently Asked Questions about issue-status-sync

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

FAQPage Schema

How do I post execution progress to GitHub Issues without closing them?▼

To post execution progress to GitHub Issues without closing them, trigger a status synchronization skill after role execution completes. It formats a progress comment using a standard template and leaves the GitHub Issue open for final management acceptance.

What is the best way to synchronize execution status to GitHub Issues for management review?▼

Synchronizing execution status to GitHub Issues for management review requires generating a DOC-003 compliant progress report. The process consumes upstream artifacts like acceptance decisions and posts a styled comment template enforcing evidence-driven reporting on the related GitHub Issue.

Can I post a progress comment on a GitHub Issue while keeping it open for acceptance?▼

Yes, you can post a progress comment on a GitHub Issue while keeping it open for acceptance. This applies when a dispatch originates from a GitHub Issue and all roles have completed their work, ensuring traceable progress updates without altering the Issue state.

How do I generate a DOC-003 report and GitHub comment template from upstream artifacts?▼

To generate a DOC-003 report and GitHub comment template from upstream artifacts, process acceptance decisions and verification results. This builds a traceable progress narrative and formats a standard GitHub comment for managerial review and controlled closure.

Why does my automated workflow prematurely close GitHub Issues when posting progress updates?▼

Automated workflows prematurely close GitHub Issues when lacking controlled closure enforcement. To prevent this, issue-status synchronization enforces issue-context validation and managerial acceptance, posting deterministic progress updates without altering the Issue state until final approval.

Do I need upstream acceptance decisions to build a traceable progress narrative on GitHub Issues?▼

Yes, you need upstream acceptance decisions and verification results to build a traceable progress narrative on GitHub Issues. Consuming these upstream artifacts ensures evidence-driven reporting and generates a DOC-003 compliant progress report for management review.