issue-creation

Drafts GitHub bug/feature issues after clarifying questions, research, duplicate/dependency checks, and user approval.

6|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/remiverdiesen/ark-fork --skill issue-creation-remiverdiesen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-creation
Source: https://github.com/remiverdiesen/ark-fork/tree/main/.claude/skills/issue-creation
Command: npx skills add https://github.com/remiverdiesen/ark-fork --skill issue-creation-remiverdiesen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns vague bug reports and feature ideas into well-researched GitHub issues, reducing guesswork, rework, and duplicate tickets.

Core Features & Use Cases

  • Clarifying intake: Always asks focused questions first so the real problem, impact, and constraints are understood before any drafting begins.
  • Codebase research: Investigates relevant files and architecture to capture accurate context for the issue without prescribing implementation details.
  • Duplicate and dependency checks: Searches existing issues in the main repository and marketplace-related repository when relevant, then records related work as references or dependencies.
  • Structured issue drafting: Produces a reviewable issue with problem, context, impact, related issues, task breakdown, and testing approach sections.
  • Approval-first workflow: Shows the full draft for user edits and approval before any issue is created.

Quick Start

Ask me to create a GitHub issue for a bug or feature, and I will first ask clarifying questions before researching the codebase and drafting the issue.

Frequently Asked Questions about issue-creation

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

FAQPage Schema
How do I create well-researched GitHub issues from vague bug reports?

Drafting GitHub issues from bug reports involves a clarifying intake to understand the real problem, followed by codebase research to capture accurate context. The issue is then structured with problem, impact, and testing sections before user approval.

How do I check for duplicate issues before creating a new GitHub ticket?

Checking for duplicate GitHub issues involves searching existing tickets in the main repository and related marketplace repositories. Related work found during this search is recorded as references or dependencies within the structured issue draft.

Can I review and edit a GitHub issue draft before it gets created?

You can review and edit a GitHub issue draft before creation using an approval-gated workflow. The full draft, including problem, context, and task breakdown, is presented for user edits and approval before any issue is created.

What is the best way to capture codebase context when drafting a GitHub issue?

The best way to capture codebase context for a GitHub issue is by investigating relevant files and architecture during research. This captures accurate context for the problem without prescribing implementation details in the drafted issue.

Does issue drafting work with marketplace-related repositories for dependency tracking?

Issue drafting supports marketplace-related repositories for dependency tracking by searching these contexts during duplicate checks. Related work found in these repositories is recorded as references or dependencies within the structured issue draft.