analyze-issue

To analyze the root cause of a ShardingSphere GitHub issue, apply a structured workflow that evaluates version, deployment, reproduction steps, and related files to produce traceable conclusions with evidence.

Evidence-based issue triage is a process that identifies root causes by referencing official docs, repository code, tests, and linked issues, ensuring conclusions are traceable and include a confidence level and recommended labels.

Triage GitHub issues with a root-cause-first approach by performing a structured intake of topology and reproduction context, then articulating the root cause and providing actionable recommendations based on repository evidence.

Yes, issue analysis requires specific deployment and reproduction details to accurately identify the root cause, demanding structured intake of topology, version, and reproduction context before generating a structured analysis.

The best way to structure a GitHub issue analysis report is using a four- to five-section format: problem, root cause, analysis, and recommendations, ensuring all conclusions reference official documentation and repository code.

You should use an evidence-first approach for ShardingSphere issue triage because it ensures conclusions are traceable to official docs and repository tests, preventing speculative fixes and providing a reliable confidence level for the analysis.