create-issue

Manage GitHub issues via local markdown files with YAML frontmatter.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/N0K0/claude-plugins-backalley --skill create-issue-n0k0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-issue
Source: https://github.com/N0K0/claude-plugins-backalley/tree/main/plugins/gh/skills/create-issue
Command: npx skills add https://github.com/N0K0/claude-plugins-backalley --skill create-issue-n0k0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually creating and managing GitHub issues through the web UI is slow and disrupts developer workflow, especially when adding structured metadata like labels, milestones, and threaded comments. This Skill eliminates that friction by letting you work with issues entirely via local markdown files that sync automatically to GitHub.

Core Features & Use Cases

  • Local Issue Creation: Draft new GitHub issues by writing simple markdown files with YAML frontmatter for title, labels, milestones, and assignees, no web UI required.
  • Comment Management: Add, update, and track comments on new or existing issues directly in the local file, with changes synced to GitHub on push.
  • Automatic Organization: Issue files are automatically renamed with their GitHub issue number and moved to a closed folder when the issue is resolved, keeping your local issue directory tidy.
  • Use Case: A developer tracking a login bug can draft the issue offline with reproduction steps, add follow-up comments as they investigate, and push all changes to GitHub in one go without switching contexts.

Quick Start

Use the create-issue skill to draft a new high-priority bug report for the mobile app crash on startup by writing a markdown file in the .issues folder with the issue title, priority label, and crash reproduction steps in the body.

Frequently Asked Questions about create-issue

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

FAQPage Schema
How do I automatically sync local markdown files to GitHub issues?

You can sync local markdown files to GitHub issues by drafting files with YAML frontmatter for metadata. The skill pushes local changes to GitHub and pulls remote updates, keeping both sides consistent.

Can I add labels, milestones, and assignees to GitHub issues without the web UI?

Yes, you can add labels, milestones, and assignees directly within your local markdown file's YAML frontmatter. This structured metadata syncs automatically to the corresponding GitHub issue on push.

What is the best way to track and manage GitHub issue comments locally?

The best way to manage GitHub issue comments locally is to add or update them directly in your markdown file. Changes sync to the GitHub issue automatically, preserving the threaded discussion without web UI interaction.

Does this approach organize closed GitHub issues automatically?

Yes, when a GitHub issue is resolved, the local markdown file is automatically renamed with its issue number and moved to a closed folder. This keeps your local issue directory tidy without manual file management.

Can I draft GitHub bug reports offline and push them all at once?

Yes, you can draft multiple GitHub bug reports offline using local markdown files with reproduction steps and metadata. All changes sync to GitHub in one go when you push, eliminating context switching.