publish-issues

Convert markdown issue files into GitHub issues via the GitHub API.

Updated Sep 18, 2020
One-click install
npx skills add https://github.com/bitpantry/BitPantry.CommandLine --skill publish-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish-issues
Source: https://github.com/bitpantry/BitPantry.CommandLine/tree/main/.github/skills/publish-issues
Command: npx skills add https://github.com/bitpantry/BitPantry.CommandLine --skill publish-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of converting staged issue markdown files into GitHub issues, streamlining the workflow for tracking and managing tasks in a team environment.

Core Features & Use Cases

  • Markdown to Issue Conversion: Converts markdown-formatted issue files into GitHub issues.
  • Spec Number Based Publication: Ensures issues are published based on a specified spec number, maintaining a structured workflow.
  • Validation and Confirmation: Provides validation for user inputs and confirms issue creation to avoid accidental or erroneous publishing.

Quick Start

Run the 'publish-issues' skill with the spec number as an argument, e.g., /publish-issues 006.

Frequently Asked Questions about publish-issues

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

FAQPage Schema
How do I convert markdown files into GitHub issues automatically?

To convert markdown files into GitHub issues, this Skill parses staged markdown content and publishes it via the GitHub API. It requires user confirmation before creating issues to prevent accidental publication.

What is spec-based publication for GitHub issue tracking?

Spec-based publication publishes GitHub issues according to a specified spec number, ensuring structured workflow management. By referencing a spec number like 006, the Skill targets the correct staged files for conversion.

How do I publish staged issues to GitHub using a spec number?

You can publish staged issues by running the publish-issues command with the spec number as an argument, such as /publish-issues 006. The Skill then validates the input and requests confirmation before creating the GitHub issues.

Can I prevent accidental issue creation when publishing markdown to GitHub?

Yes, this Skill provides validation for user inputs and requires explicit user confirmation before publishing. This mechanism ensures you can review and prevent accidental or erroneous GitHub issue creation.

Does this GitHub issue publisher require any external dependencies?

No, this Skill does not require any external dependencies to convert markdown files into GitHub issues. It operates independently using the provided scripts and references to manage the publication workflow.