new-issue

Generates GitHub issues with code-grounded verification and complexity scoring via CLI integration.

45|7|Updated Jul 4, 2026

Search Tags:#automation #workflow #development #github #issue #tracking

Ready to run

npx skills add https://github.com/richkuo/rk-skills --skill new-issue-richkuo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: new-issue
Source: https://github.com/richkuo/rk-skills/tree/main/skills/new-issue
Command: npx skills add https://github.com/richkuo/rk-skills --skill new-issue-richkuo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the creation of vague, incomplete, or duplicate GitHub issues by enforcing rigorous verification against the codebase and ensuring every issue is fully specified before filing.

Core Features & Use Cases

Code-Grounded Verification: Automatically traces claims to specific file and line references to ensure factual accuracy.
Complexity Scoring: Applies a standardized formula to assign complexity scores and routing signals, ensuring consistent issue prioritization.
Use Case: When a bug is identified during a conversation, use this skill to generate a complete, actionable issue that includes a problem statement, goal, approach, and acceptance criteria, ready for immediate implementation.

Quick Start

Use the new-issue skill to create a GitHub issue based on the bug we just discussed in this conversation.

Frequently Asked Questions about new-issue

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

FAQPage Schema

How do I create fully specified GitHub issues automatically from a conversation?▼

To create fully specified GitHub issues, this skill generates complete tickets with problem statements, goals, approaches, and acceptance criteria directly from your conversation context. It enforces rigorous verification against the codebase before filing.

How does code-grounded verification work when tracking GitHub issues?▼

Code-grounded verification traces claims to specific file and line references to ensure factual accuracy. This mechanism grounds the GitHub issue creation process in actual code paths, eliminating vague or inaccurate bug reports.

Do I need GitHub CLI integration to automate issue creation?▼

Yes, GitHub CLI integration is required to perform repository lookups and issue creation. This prerequisite allows the skill to access your codebase for verification and automatically file the standardized technical documentation.

What is complexity scoring in GitHub issue tracking and how does it help prioritization?▼

Complexity scoring applies a standardized formula to assign scores and routing signals to GitHub issues. This ensures consistent issue prioritization by evaluating the technical scope required for implementation.

How do I prevent duplicate GitHub issues in an automated development workflow?▼

To prevent duplicate GitHub issues, this skill performs automated duplicate detection by grounding claims in existing code paths. It verifies facts against the repository before creating a new ticket.

Can I standardize technical documentation for bugs found during development?▼

Yes, you can standardize technical documentation by generating GitHub issues that adhere to project-specific formatting conventions. Every issue includes a complete problem statement, goal, approach, and acceptance criteria.