github-issues

Create and update GitHub issues with duplicate detection and repository-derived metadata.

3|Updated Apr 8, 2025
One-click install
npx skills add https://github.com/ZanzyTHEbar/dragonarchy --skill github-issues-zanzythebar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issues
Source: https://github.com/ZanzyTHEbar/dragonarchy/tree/main/packages/opencode/.config/opencode/skills/github-issues
Command: npx skills add https://github.com/ZanzyTHEbar/dragonarchy --skill github-issues-zanzythebar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating GitHub issues manually often leads to duplicates, hardcoded repository details, broken Markdown formatting, and accidental leakage of sensitive information. This Skill enforces a safe, consistent workflow for issue creation and updates using the GitHub CLI. ## Core Features & Use Cases - Duplicate Detection: Searches for existing issues with the same title or intent before creating anything new, reusing or updating matches instead. - Repository-Derived Metadata: Derives owner, repository, and default branch from gh repo view instead of hardcoding values, and verifies authentication with gh auth status. - Safe Formatting and Boundaries: Uses temporary body files passed with --body-file so Markdown survives shell parsing, and refuses to commit, push, or include secrets in issue content. - Use Case: After discovering a bug during development, ask the assistant to file an issue; it checks for an existing report, writes a body with context and testable acceptance criteria, applies meaningful labels, and confirms the resulting issue URL. ## Quick Start Ask the assistant to create a GitHub issue for the bug you just found, including reproduction steps and acceptance criteria.

Frequently Asked Questions about github-issues

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

FAQPage Schema
How do I create a GitHub issue from the command line?

Use the GitHub CLI with gh issue create, passing the body via a temporary file with --body-file so Markdown newlines survive shell parsing. Verify authentication first with gh auth status and derive the repository with gh repo view.

How to avoid creating duplicate GitHub issues?

Search for an existing issue with the same title or intent before creating anything, using gh issue list or search queries. If a match exists, reuse or update that issue rather than opening a duplicate.

Why does my GitHub issue body lose Markdown formatting?

Passing multi-line Markdown directly as a shell argument breaks newlines during parsing. Write the body to a temporary file and pass it with -F or --body-file so the formatting is preserved exactly.

Can this skill also create pull requests or push commits?

No. The skill explicitly does not commit, push, create branches, or open pull requests. Those actions require a separately invoked and approved shipping workflow.

What should never be included in a GitHub issue body?

Never include secrets, credentials, tokens, or private raw logs in issue content. Issues are often publicly visible, so sensitive data must be redacted before filing.