csdlc-issue

Draft structured GitHub issues from session context and create them with gh.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/danhannah94/claymore-plugins --skill csdlc-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: csdlc-issue
Source: https://github.com/danhannah94/claymore-plugins/tree/main/csdlc/skills/csdlc-issue
Command: npx skills add https://github.com/danhannah94/claymore-plugins --skill csdlc-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables users to convert ongoing conversation context into structured GitHub issues, reducing context-switching and ensuring critical problems, features, and debts are tracked in the appropriate repository.

Core Features & Use Cases

  • Determine the target repository from user-provided flags, the current git remote, or NEXT.md context, and draft a well-structured issue.
  • Classify the issue type (Bug, Feature, Tech debt, or Task) to apply suitable description sections and labels.
  • Present the draft for review and then create the issue with gh issue create, returning the URL and number for traceability.

Quick Start

Tell the AI to file a GitHub issue in the correct repository using the current session context.

Frequently Asked Questions about csdlc-issue

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

FAQPage Schema
How do I create a GitHub issue from an ongoing AI chat context?

You can create a GitHub issue from conversation context by having the AI draft a structured report and execute gh issue create. This Skill automatically categorizes the issue as a bug, feature, or tech debt and pushes it to the target repository.

Can I specify a target GitHub repository when generating an issue?

Yes, you can specify a target repository when generating an issue by using the optional --repo override flag. The Skill also automatically determines the repository from your current git remote or NEXT.md file if no override is provided.

How do I automatically format bug reports and feature requests for GitHub?

Automatically formatting bug reports and feature requests requires classifying the issue type and applying suitable description sections. This Skill identifies the type, structures reproduction steps and context, and applies appropriate labels before creation.

Does this issue tracking automation work without the GitHub CLI installed?

No, this issue tracking automation requires the GitHub CLI to function because it uses the gh issue create command to submit the drafted issue. The CLI handles the authentication and direct creation of the issue in the target repository.

What is the best way to track tech debt discovered during a development session?

Tracking tech debt discovered during a session is best handled by immediately converting the context into a labeled GitHub issue. This Skill drafts the technical debt details, adds appropriate labels, and creates the issue to ensure it is not lost.

How do I add labels to GitHub issues generated from session context?

Adding labels to GitHub issues generated from session context happens automatically based on issue classification. The Skill determines if the issue is a bug, feature, or tech debt and applies the appropriate label set during the gh issue create execution.