issue-generation

Convert conversations into structured GitHub issues with mandatory redaction and confirmation.

Updated Nov 24, 2025
One-click install
npx skills add https://github.com/ByronWilliamsCPA/.claude --skill issue-generation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-generation
Source: https://github.com/ByronWilliamsCPA/.claude/tree/main/.claude/skills/issue-generation
Command: npx skills add https://github.com/ByronWilliamsCPA/.claude --skill issue-generation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of losing actionable items from team conversations and the danger of accidentally leaking sensitive data like secrets or PII when manually filing GitHub issues.

Core Features & Use Cases

  • Conversation to Scoped Issue: Distills discussions or single utterances into structured GitHub issues with clear titles, problem statements, acceptance criteria, and context links, splitting multi-concern threads into separate issues.
  • Mandatory Redaction Gate: Automatically scans drafted issues for secrets, PII, and internal-only references before filing, replacing sensitive content with placeholders and re-confirming with you.
  • Explicit Confirmation Workflow: Requires your explicit approval of the final issue draft (including labels and assignees) before filing, preventing unwanted tracker entries. Use case: After a product team discussion about adding two-factor authentication, use this Skill to generate a properly formatted, redacted GitHub issue and approve it for filing in one workflow.

Quick Start

Use the issue-generation skill to turn our recent discussion about the payment processing bug into a GitHub issue for the backend engineering team.

Frequently Asked Questions about issue-generation

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

FAQPage Schema
How do I convert team conversations into structured GitHub issues?

To convert conversations into GitHub issues, this Skill distills discussions or single utterances into structured issues with clear titles, problem statements, and acceptance criteria, splitting multi-concern threads into separate issues.

How does PII redaction work when generating GitHub issues from chat logs?

PII redaction works through a mandatory pre-filing gate that automatically scans drafted issues for secrets, PII, and internal-only references, replacing sensitive content with placeholders before you file the issue.

Can I review and edit a drafted GitHub issue before it gets filed?

Yes, you can review drafted issues because the workflow requires explicit user confirmation of the final issue draft, including labels and assignees, to prevent unwanted tracker entries before filing.

What is the best way to track actionable items from project planning discussions on GitHub?

The best way to track actionable items from discussions is generating structured, scoped GitHub issues that enforce PII redaction and align with conventional commit labeling conventions for safe, consistent issue tracking.

Does issue generation support conventional commit labeling for project tracking?

Yes, issue generation supports conventional commit labeling conventions to ensure safe, consistent issue tracking across software development and project management workflows without manual formatting.

What happens if a conversation contains multiple feature requests for project tracking?

If a conversation contains multiple feature requests, the Skill splits multi-concern threads into separate, scoped GitHub issues so each actionable item is tracked independently.