newissue

Converts rough ideas into self-contained GitHub issues filed via the gh CLI.

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/rogadev/orc-pack --skill newissue-rogadev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: newissue
Source: https://github.com/rogadev/orc-pack/tree/main/skills/newissue
Command: npx skills add https://github.com/rogadev/orc-pack --skill newissue-rogadev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Rough ideas discussed in a coding session often never become actionable work items, or get filed as vague issues that no one can execute later. This Skill investigates the codebase, checks the issue board for duplicates and conflicts, and files a detailed GitHub issue that a fresh agent could execute with zero prior context. ## Core Features & Use Cases - Evidence-grounded investigation: Reads the actual code, cites file:line references, checks git history, and verifies the claim still holds on the current branch before writing anything. - Board hygiene checks: Detects duplicates (including recently closed issues), direction drift against open issues, and dependency relationships (blocked by, blocks, parent/child) before filing. - Structured issue authoring: Produces issues with a plain-language summary for stakeholders, technical detail for executors, evidence, scope boundaries, and an observable "Done when" condition; supports splitting into multiple issues or epics. - Use Case: After discussing a bug where several tools break on the deployed site, say "/newissue" and the Skill investigates the code, confirms the bug still exists, checks the board, and files a labeled, cross-linked GitHub issue with reproduction evidence. ## Quick Start Ask the assistant to turn the bug or feature idea you just discussed into a GitHub issue using the newissue skill.

Frequently Asked Questions about newissue

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

FAQPage Schema
How do I turn a rough idea into a GitHub issue with an AI agent?

Invoke the skill with "/newissue <rough idea>" or with no argument to file the topic just discussed. It investigates the code, checks the board for duplicates, then files the issue with gh issue create and returns the URL.

How does the skill check for duplicate GitHub issues before filing?

It lists open issues and recently closed issues with gh issue list, then compares the new idea against both. Genuine duplicates are reported instead of filed, while near-misses get filed with cross-links.

Can I customize labels and issue format per repository?

Yes. Per-repo house rules live in .claude/newissue.local.md or a section in AGENTS.md or CLAUDE.md, and they override defaults. Without them, the skill falls back to gh label list and .github/ISSUE_TEMPLATE/.

Does the skill require the GitHub CLI to file issues?

Yes, it relies on the gh CLI for repo inspection, label listing, board checks, and issue creation. If gh is not authenticated or the directory is not a GitHub repo, the skill stops and reports the problem.

When should work be split into multiple issues or an epic?

Split when the seed bundles unrelated work or is too large for one agent run, giving each issue its own Done when condition. Use an epic only for large interconnected work needing a roadmap, with child issues linked both ways.