issue-create

Creates structured Markdown issue documents from guided user interviews.

2|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/cc-claws/cc-code --skill issue-create-cc-claws
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-create
Source: https://github.com/cc-claws/cc-code/tree/main/.claude/skills/issue-create
Command: npx skills add https://github.com/cc-claws/cc-code --skill issue-create-cc-claws

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps turn vague user complaints, bug reports, technical debt notes, and refactoring requests into clear, structured issue documents. It is designed for situations where an AI needs to interview the user, capture observable symptoms, and produce a triage-ready record without jumping into root-cause analysis.

Core Features & Use Cases

  • Guided issue interviews: Asks one focused question at a time to clarify what happened, when it happened, and how it looks from the user’s perspective.
  • Issue normalization: Detects whether the report is a bug, performance problem, technical debt item, refactor request, security risk, or documentation gap.
  • Lifecycle-aware documentation: Checks for related existing issues, records status transitions, and writes standardized markdown for downstream triage workflows.
  • Use case: A developer says an agent UI is showing duplicate content after tool calls, and this Skill captures the symptoms, reproduction details, and affected files in a reusable issue file.

Quick Start

Tell the skill that you want to record a problem, then answer its single-question interview until it creates a structured issue document.

Frequently Asked Questions about issue-create

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

FAQPage Schema
How do I create a structured bug report from a vague user complaint?

You can create a structured bug report by using a guided issue interview that asks one question at a time to clarify observable symptoms and reproduction details, ultimately generating a standardized markdown file for triage.

What is the best way to document technical debt and refactoring requests?

Documenting technical debt and refactoring requests involves normalizing the report type, checking for related existing issues, and recording lifecycle metadata in a standardized markdown document for downstream workflows.

Can I use a guided interview to capture security concerns and documentation gaps?

Yes, you can use a guided interview to capture security concerns and documentation gaps by answering focused questions about what happened and when, which are then normalized into a triage-ready issue record.

How do I normalize user-reported problems into different issue categories?

You normalize user-reported problems by detecting whether the report describes a bug, performance problem, technical debt item, refactor request, security risk, or documentation gap during the interview process.

Does this issue creation process check for related existing issues before generating a markdown file?

Yes, the issue creation process checks for related existing issues and records status transitions before writing the final standardized markdown file to ensure accurate lifecycle-aware documentation.

When should I avoid using an automated interview for issue triage?

You should avoid using an automated interview for issue triage when your problem requires immediate root-cause analysis, as this Skill specifically focuses on capturing observable symptoms without jumping into root-cause resolution.