django-ticket-triage is a Claude Code command designed to facilitate the analysis and triaging of Django Trac tickets prior to contribution. This tool streamlines the ticket review process by automating key tasks and generating comprehensive reports.

Key Features

Ticket Analysis with /triage

By executing the command /triage <ticket_id>, this tool offers several functionalities:

• Fetches Ticket Details: Retrieves essential information, status, and the complete comment history of the ticket.
• Duplicate and Related Ticket Search: Identifies related tickets across various platforms including Trac, GitHub PRs, and Django Forum.
• Source Code Location: Pinpoints relevant portions of the Django codebase associated with the ticket.
• Ticket Validity Evaluation: Differentiates between bugs and features, assesses reproducibility, and defines the ticket's scope.
• Structured Triage Reports: Delivers a detailed report with actionable recommendations for the ticket in question.

Implementation Planning with /impl-plan

To assist in planning the implementation, run /impl-plan <ticket_id> to:

• Context Loading: Access the existing triage report to understand the ticket background.
• Deep Code Analysis: Investigate the target code and relevant tests.
• Implementation Options: Generate 2-4 viable options (A/B/C) for addressing the ticket.
• Trade-off Comparison: Analyze complexity, risk factors, and compatibility issues to compare the proposed solutions.
• Recommended Approach: Provide a selected strategy along with an implementation checklist.

Language Support

The tool supports multiple languages, allowing for locale-specific reports. For instance, a Korean report can be generated by using:

/triage 36640 ko
/impl-plan 36640 ko

Output Files

Generated reports are saved in specific directories for easy access:

• Triage Reports: Located at triage-reports/<ticket_id>.md
• Implementation Reports: Found at impl-reports/<ticket_id>.md

Limitations

While django-ticket-triage enhances the analysis process, it is essential to note the following limitations:

• Final decision-making regarding triage still requires human intervention.
• The reliability of the analysis is contingent upon the available ticket comments and history.
• Additional context (e.g., W3C specifications, screen reader support) might necessitate manual verification.

Explore the examples directory for sample reports that illustrate the output of this powerful tool.