gh-post-issue-update

Post structured markdown updates to GitHub issues via gh CLI.

18|5|Updated Nov 3, 2025
One-click install
npx skills add https://github.com/mvillmow/ProjectOdyssey --skill gh-post-issue-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-post-issue-update
Source: https://github.com/mvillmow/ProjectOdyssey/tree/main/.claude/skills/gh-post-issue-update
Command: npx skills add https://github.com/mvillmow/ProjectOdyssey --skill gh-post-issue-update

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh.

What problem does it solve?

Manually updating GitHub issues with progress, findings, or design decisions can be inconsistent, lack structure, and consume valuable development time.

Core Features & Use Cases

  • Structured Updates: Posts implementation notes, status updates, design decisions, and completion summaries with clear formatting.
  • Audit Trail: Creates a consistent audit trail of work done, decisions made, and blockers encountered directly on the issue.
  • Use Case: As you make significant progress on an issue, use this skill to post a "Progress Update" comment, detailing completed tasks, current work, and any new findings.

Quick Start

Use the gh-post-issue-update skill to post a "Progress Update" comment to GitHub issue #123, detailing completed and in-progress tasks.

Frequently Asked Questions about gh-post-issue-update

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

FAQPage Schema
How do I post structured updates to GitHub issues automatically?

Post structured updates to GitHub issues by using the gh-post-issue-update skill with the gh CLI. It automates appending progress reports, design decisions, blockers, and completion summaries directly to issues as formatted comments, eliminating manual updates and ensuring consistency.

Can I use GitHub issue comments to create an audit trail of project work?

Yes. Posting structured updates to GitHub issues creates a consistent audit trail by appending timestamped comments with implementation notes, status changes, and decisions directly to the issue, making work history transparent and discoverable.

What's the best way to document progress on GitHub issues during development sprints?

Document progress by posting structured updates to GitHub issues during sprints. The skill supports heredoc input, file-based content, and markdown sections, enabling you to append detailed progress notes, completed tasks, and blockers as formatted issue comments without manual formatting.

Does gh-post-issue-update work with markdown content and templates?

Yes. The skill supports markdown content, template-driven sections, and heredoc input, allowing you to post richly formatted updates to GitHub issues with consistent structure and styling across multiple issue comments.

Can I automate GitHub issue updates without manually editing each comment?

Yes. Automate GitHub issue updates by integrating the gh CLI with this skill to append progress reports and design rationales programmatically. It eliminates manual editing and ensures updates are posted consistently with predefined structure.

What prerequisites do I need to post updates to GitHub issues?

You need the gh CLI installed and authenticated to your GitHub account. The skill uses gh as its dependency to interact with GitHub issues, enabling you to post structured updates directly from your development workflow.