skills.rest
getty104
getty104COMMUNITY
Explore all skills by this author →
Website𝕏@getty104GitHub

post-issue-body

Format and post GitHub Issue bodies via gh CLI commands.

4|1|Updated Feb 14, 2026
Search Tags:#ci/cd#github#github issue#issue automation#markdown formatting
One-click install
npx skills add https://github.com/getty104/claude-task-worker --skill post-issue-body
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: post-issue-body
Source: https://github.com/getty104/claude-task-worker/tree/main/plugin/skills/post-issue-body
Command: npx skills add https://github.com/getty104/claude-task-worker --skill post-issue-body

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the formatting and posting of GitHub Issue bodies, streamlining the issue creation and update process.

Core Features & Use Cases

  • Automated Issue Formatting: Formats GitHub Issue bodies according to a strict template, ensuring consistency across all issues.
  • Pre-Posting Checklist: Runs a checklist before posting to ensure all required fields are present and correctly formatted.
  • Issue Creation/Update: Executes gh issue create or gh issue edit to post the formatted body to GitHub.
  • Follow-Up Comment Posting: Optionally posts a follow-up comment with confirmation items.

Quick Start

Use the post-issue-body skill to format and post a new issue with the title "New Feature Request" and content provided in the input YAML.

Frequently Asked Questions about post-issue-body

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

FAQPage Schema
How do I automate GitHub Issue body formatting and posting?▼

Automating GitHub Issue body formatting is achieved by using a Skill that applies a strict template, runs a pre-posting checklist, and executes `gh issue create` or `gh issue edit` commands to post the formatted content directly to GitHub.

What is the best way to ensure consistent markdown formatting across GitHub issues?▼

The best way to ensure consistent markdown formatting across GitHub issues is to use an issue automation Skill that enforces a strict template, validates required fields via a pre-posting checklist, and optionally posts follow-up comments with confirmation items.

Does the GitHub issue automation process require specific input formats?▼

Yes, the GitHub issue automation process requires proper YAML input for issue details, providing the necessary structure for the Skill to format the body and coordinate the execution of `gh issue create` or `gh issue edit` commands.

How does the automated issue creation process handle follow-up comments?▼

The automated issue creation process optionally posts a follow-up comment to the newly created or edited GitHub issue, appending confirmation items after the main issue body has been successfully formatted and posted via the `gh` CLI.

Can I use this approach to edit existing GitHub issues or is it only for creating new ones?▼

You can use this approach to edit existing GitHub issues as well as create new ones, because the Skill coordinates the execution of both `gh issue create` and `gh issue edit` commands within a GitHub context to manage issue bodies.

Related Skills

Explore More Software Engineering Skills→
SantiagoisperSantiagoisper

ce-report-bug

Create structured GitHub issues for compound-engineering plugin bugs via GitHub CLI.

Community
Intermediate
lushly-devlushly-dev
4

manage-projects

Orchestrate GitHub Projects, issues, and parallel Claude agent waves for feature lifecycle management.

Official
Advanced
gagan114662gagan114662

github

Manage GitHub repositories, pull requests, issues, and Actions workflows via gh CLI and APIs.

Community
Intermediate
tankpkgtankpkg
1

@tank/github-issues

Manage GitHub Issues lifecycle with gh CLI and GitHub Platform.

Official
Advanced