ticket-description

Generate structured technical issue descriptions from git diffs or requirements.

Updated Jul 6, 2026
One-click install
npx skills add https://github.com/brenordv/claude-skill-set --skill ticket-description
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ticket-description
Source: https://github.com/brenordv/claude-skill-set/tree/main/skills/ticket-description
Command: npx skills add https://github.com/brenordv/claude-skill-set --skill ticket-description

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the inconsistency and manual effort involved in writing high-quality technical tickets by reverse-engineering them from existing code changes or structured user intent.

Core Features & Use Cases

  • Retroactive Documentation: Automatically generates a ticket title and description based on the diffs of your current branch.
  • Interactive Drafting: Guides you through a focused Q&A to define the problem, scope, and acceptance criteria for new work.
  • Vault Integration: Ensures consistency by retrieving and mirroring the structure of similar past tickets from your personal vault.

Quick Start

Ask the assistant to draft a ticket for the current branch changes using the ticket-description skill.

Frequently Asked Questions about ticket-description

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

FAQPage Schema
How do I generate technical issue descriptions from git diffs automatically?

You can generate structured technical issue descriptions by analyzing your current branch's git diffs. The skill reverse-engineers consistent ticket titles and documentation from existing code changes, eliminating manual drafting effort and ensuring standardized technical writing across your workflow.

What is the best way to standardize bug fix and feature documentation across a development team?

Standardizing bug fix and feature documentation is achieved by validating generated issue descriptions against privacy standards and archiving results in a local vault. This ensures consistent tracking of design decisions and technical issues across software development workflows.

Can I create structured issue tracking tickets interactively without existing code changes?

Yes, you can create issue tracking tickets interactively without existing code changes. The skill guides you through a focused Q&A to define the problem, scope, and acceptance criteria for new work, ensuring structured documentation even before development begins.

Does the ticket drafting process support retrieving past ticket structures for consistency?

The ticket drafting process supports retrieving and mirroring similar past ticket structures from your personal vault. This vault integration ensures consistency in technical writing by applying previously established documentation patterns to new issue descriptions.

How do I ensure generated technical tickets do not expose sensitive data?

To ensure generated technical tickets do not expose sensitive data, the skill validates all output against privacy standards before archiving. This automated check prevents confidential information from being included in your issue tracking documentation or local vault.