csa-issue-reporter

To automate GitHub issue creation for CLI errors, describe the operational failure to trigger automatic report generation. The tool collects environment context like OS and rustc version, classifies the error, and invokes gh issue create to file the report.

An automated GitHub issue triage report includes environment context such as csa version, OS, rustc version, and the latest commit hash. It also features error classification labels and a structured body formatted using Conventional Commits style for consistent triage.

Yes, you can use automated issue reporting for CI/CD workflows. The structured issue creation process is reusable for incident reports, allowing continuous integration pipelines to automatically document operational failures like parse failures or session state corruption.

Conventional Commits formatting helps with GitHub issue triage by enforcing a consistent title structure across all automated reports. This standardization allows maintainers to quickly categorize and process operational errors like quota exhaustion or tool not found errors.

Operational errors that can be automatically reported to GitHub include quota exhaustion, crashes, parse failures, session state corruption, and tool not found errors. Each error type is classified with appropriate labels for structured triage.