create-new-issue

Convert informal issue details into formal Wrangler MCP issues via the issues_create tool.

4|1|Updated Oct 29, 2025
One-click install
npx skills add https://github.com/samjhecht/wrangler --skill create-new-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-new-issue
Source: https://github.com/samjhecht/wrangler/tree/main/skills/create-new-issue
Command: npx skills add https://github.com/samjhecht/wrangler --skill create-new-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

New issues or tasks are often captured inconsistently or incompletely, leading to miscommunication, missed details, and disorganized project tracking, hindering efficient development.

Core Features & Use Cases

  • Structured Issue Creation: Analyzes provided issue details and converts them into a well-structured markdown file using predefined templates (bug or task).
  • Comprehensive Frontmatter: Populates the YAML frontmatter with relevant metadata like ID, title, status, priority, and labels.
  • Detailed Sections: Ensures all sections (Summary, Reproduction Steps, Solutions Attempted, Diagnostics, References) are filled out comprehensively.
  • Use Case: When a new bug, feature, or outstanding task has been identified and needs to be formally captured in a comprehensive issue file for tracking and collaboration.

Quick Start

A user reported a bug: "Login button doesn't work on mobile." Create a new bug issue for this.

Frequently Asked Questions about create-new-issue

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

FAQPage Schema
How do I create a structured issue from informal bug reports?

This Skill transforms informal issue details into formal, standards-compliant issues by analyzing the problem, selecting the appropriate issue type (bug, task, feature, or specification), and populating all required metadata fields automatically. It ensures consistent formatting and comprehensive documentation across your project.

What should I include when reporting a bug to ensure it's properly documented?

Provide the informal bug details—what happened, steps to reproduce, and any context. The Skill converts this into a complete issue with structured sections including summary, reproduction steps, solutions attempted, diagnostics, and references, ensuring nothing is missed.

Can I use this to organize tasks and feature requests alongside bug reports?

Yes. The Skill dynamically selects the correct issue type based on your input, handling bugs, tasks, features, and specifications. All types receive the same structured treatment with comprehensive frontmatter and standardized markdown templates for consistent project organization.

How does this prevent miscommunication and lost details in issue tracking?

By enforcing a mandatory announcement and structured creation process, the Skill ensures all issues include required metadata, validation checks, and auditable post-creation records. This eliminates incomplete submissions and keeps team communication clear and traceable.

What makes this different from manually writing issue templates?

This Skill automates the entire conversion process—analyzing your description, selecting the appropriate type, populating YAML frontmatter, filling template sections, and validating successful creation. Manual templates require you to remember and fill each field; this handles it end to end.

Do I need special knowledge to format issues correctly?

No. You provide informal issue details in natural language. The Skill handles all formatting, structure, and standards compliance automatically, converting your input into properly formatted MCP issues without requiring knowledge of templates or metadata fields.