issue-new

Automate GitHub issue filing and update INDEX.md documentation.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/mikersays/mikersays-plugins --skill issue-new
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-new
Source: https://github.com/mikersays/mikersays-plugins/tree/main/plugins/issues/skills/issue-new
Command: npx skills add https://github.com/mikersays/mikersays-plugins --skill issue-new

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, read, write, edit, glob, grep, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of filing and managing issues for bugs, feature requests, incidents, or open questions, ensuring they're properly tracked and easy to access.

Core Features & Use Cases

  • Quick Issue Logging: Log new issues with minimal command input.
  • Structured Ticketing: Automatically generates tickets with pre-filled templates based on conversation context.
  • Documentation: Maintains an organized INDEX.md of all issues for quick reference.
  • Collaboration: Enhances collaboration by ensuring all relevant information is recorded and accessible.

Quick Start

Use the command /issue-new <issue title> to create a new ticket for your issue.

Frequently Asked Questions about issue-new

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

FAQPage Schema
How do I automate GitHub issue tracking and bug reporting from a conversation?

You can automate GitHub issue tracking by parsing conversation context to generate structured ticket files and populate issue documentation automatically. This Skill creates pre-filled templates for bug reporting and feature requests, then updates an index file to maintain organized tracking for collaboration.

What is the best way to log a new feature request or bug report in a GitHub repository?

The best way to log a new feature request or bug report is using the quick start command to generate a structured ticket. This automatically populates the ticket content with relevant details from your conversation and maintains an organized INDEX.md file for quick reference and collaboration.

Does this issue filing Skill require any specific environment setup or dependencies?

Yes, this Skill requires bash, read, write, edit, glob, and grep tools to function properly. These dependencies are used to parse user input, generate ticket files, and update the issue documentation index within your GitHub repository.

Can I use this ticketing system to maintain an organized index of all reported issues?

Yes, this ticketing system automatically maintains an organized INDEX.md file of all issues for quick reference. It streamlines the process of filing and managing bugs, feature requests, incidents, or open questions, ensuring all relevant information is properly tracked and easy to access.

How does structured ticketing work when filing a new issue?

Structured ticketing works by automatically generating tickets with pre-filled templates based on conversation context. It parses your input to populate issue ticket content, ensuring all relevant information for bugs or feature requests is recorded systematically and accessible for collaboration.

Why should I use an automated issue logging command instead of manually creating GitHub tickets?

Automated issue logging streamlines filing and managing issues for bugs, feature requests, incidents, or open questions, ensuring they are properly tracked and easy to access. It eliminates manual template population by generating structured ticket files directly from conversation context and maintaining an organized index.