skills.rest
jforksy
jforksyCOMMUNITY
Explore all skills by this author →
𝕏@jeff_forkanGitHub

create-issue

Capture mid-flow issues into structured tickets with labels and details.

Updated Aug 27, 2026
Search Tags:#workflow#development#feature#ticket#issue#bug#capture
One-click install
npx skills add https://github.com/jforksy/claude-skills --skill create-issue-jforksy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-issue
Source: https://github.com/jforksy/claude-skills/tree/main/create-issue
Command: npx skills add https://github.com/jforksy/claude-skills --skill create-issue-jforksy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers quickly convert mid-flow thoughts into complete issue tickets, reducing context switching and accelerating debugging and feature work.

Core Features & Use Cases

  • Structured issue capture: generates a complete issue with title, TL;DR, current behavior vs expected behavior, touched files, risks/notes, and proper type/priority/effort labels.
  • Context-aware prompts: asks targeted questions to fill gaps when the user is mid-work.
  • Use Case: while coding, you notice a bug or improvement; create a ticket without leaving the IDE or chat.

Quick Start

Example: "Create an issue for the login bug where the password reset fails under SSO; include steps to reproduce and affected module."

Frequently Asked Questions about create-issue

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

FAQPage Schema
How do I create a structured bug ticket from a mid-flow development issue?▼

To create a structured bug ticket, describe the issue and the tool prompts you for a clear title, TL;DR, current versus expected behavior, touched files, and risks to generate a complete ticket.

What information should a feature ticket include for development workflows?▼

A feature ticket should include a title, TL;DR, current versus expected behavior, touched files, risks, and proper type, priority, and effort labels to maintain a clear development workflow.

Can I capture improvement tickets without leaving my codebase?▼

Yes, you can capture improvement tickets within your codebase by applying this issue capture tool to mid-flow thoughts, reducing context switching and accelerating debugging.

Does this issue capture tool work for bugs, features, and improvements?▼

Yes, this issue capture tool works for bugs, features, and improvements across codebases by applying context-aware prompts to enforce complete and structured tickets.

What is the best way to label issue priority and effort for a new ticket?▼

The best way to label issue priority and effort is to let the ticket generation tool prompt you for proper type, priority, and effort labels during the structured capture process.

Related Skills

Explore More Software Engineering Skills→
aaronbrethorstaaronbrethorst
5

user-story-creator

Generate user stories from URLs, ticket numbers, or summaries with acceptance criteria.

Community
Advanced
DavidsonGomesDavidsonGomes

evo-pm

Coordinate sprint planning, task assignment, and status reporting for cross-functional teams.

Community
Intermediate
AnveioAnveio
1

task-pull-request

Automate GitHub pull request creation, reviews, feedback, and merges via gh CLI.

Community
Intermediate
dealroom-aidealroom-ai

linear-issue-writing

Draft structured Linear issues with Problem, Solution, and Acceptance Criteria sections.

Official
Advanced