skills.rest
VIPER-Metrics
VIPER-MetricsOFFICIAL
Explore all skills by this author →
GitHub

create-issue

Create well-documented GitHub issues through structured questions and code context.

1|Updated Jan 19, 2026
Search Tags:#github#issue-tracking#codebase-context#acceptance-criteria#create-issue#interactive-questions
One-click install
npx skills add https://github.com/VIPER-Metrics/claude-code-skills --skill create-issue-viper-metrics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-issue
Source: https://github.com/VIPER-Metrics/claude-code-skills/tree/main/skills/create-issue
Command: npx skills add https://github.com/VIPER-Metrics/claude-code-skills --skill create-issue-viper-metrics

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Creating GitHub issues is often a manual, repetitive task. This skill guides users through structured questioning and context gathering to produce a complete, well-labeled issue with clear acceptance criteria.

## Core Features & Use Cases

  • Interactive questionnaire that determines issue type, scope, and required details.
  • Context-aware guidance that reads codebase context and related files to inform the issue description.
  • Output-ready GitHub issue with labels, acceptance criteria, and suggested structure.

### Quick Start Use the create-issue command to start an interactive session and generate a ready-to-create GitHub issue.

Frequently Asked Questions about create-issue

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

FAQPage Schema
How do I create well-documented GitHub issues with acceptance criteria?▼

To create well-documented GitHub issues, this skill guides you through structured interactive questions to define the type, component, description, and acceptance criteria for bug reports or feature requests. It reads your codebase context to inform the final issue structure.

Can I generate GitHub issues by reading codebase context and related files?▼

Yes, you can generate GitHub issues informed by codebase context. The skill reads related files during the interactive session to ensure the resulting issue description accurately reflects the relevant code and project structure.

What is the best way to automate issue tracking setup for feature requests?▼

Automating issue tracking setup is best handled by using the create-issue command to start an interactive session. This guides you through defining issue scope, type, and acceptance criteria to output a ready-to-create GitHub issue with suggested labels.

Does this issue generation process apply to both bug reports and codebase improvements?▼

Yes, this issue generation process applies to bug reports, feature requests, and codebase improvements. The interactive questionnaire adjusts its structured questions to satisfy the specific requirements for whichever issue type you are documenting.

How do I ensure my GitHub issues include suggested labels and related files?▼

To ensure GitHub issues include suggested labels and related files, the skill automatically gathers these details during the interactive questioning phase. It structures your responses into an output-ready issue complete with required metadata.

What are the limitations of using interactive questions for issue tracking?▼

The limitation of using interactive questions for issue tracking is that it requires manual input during the session. While it reads codebase context to inform the description, you must still actively answer the structured questions to generate the final issue.

Related Skills

Explore More Software Engineering Skills→
wachawowachawo

qa

Gather user context and codebase insights to create GitHub issues.

Community
Advanced
thrawn01thrawn01
11

fix-issue

Reproduce GitHub issues end-to-end and fix them with test-driven development.

Community
Advanced
yuridefrancayuridefranca

component-mapper

Map affected components, dependencies, and data flow for a reported bug.

Community
Intermediate
paulchiupaulchiu
3

write-pull-request

Generate pull request descriptions from git diff and commit history.

Community
Intermediate