[Auto-Triage] Auto-triage summary for scheduled unlabeled issues

[github-actions[bot]]

🏷️ Auto-Triage Report Summary

Report Period: 2026-07-11 scheduled run
Issues Processed: 2
Labels Applied: 7 total labels
Still Unlabeled: 0 issues from this batch

Key Metrics

• Success Rate: 100%
• Average Confidence: Medium
• Most Common Classifications: bug (2), workflows (1), mcp (1)

Classification Summary

Issue	Applied Labels	Confidence	Key Reasoning
#44844	bug, cli, mcp, security	High	Repro report for missing GitHub MCP tools in Claude Code; mentions gh aw, MCP servers, and security-impacting false negative
#44842	bug, workflows, needs-triage	Medium	Reports schema/validation problem in safe-output tooling; clearly a bug, touches workflow tooling, but broad tool-surface classification remains somewhat ambiguous

View Detailed Classification Analysis

Detailed Breakdown

Issue #44844

• Detected repeated failure language: "failed", "failure rate", "actual behavior"
• Strong component signals: gh aw, workflow YAML, MCP server/tool registration
• Included security because the report cites a silent false negative on a critical CVE workflow
• Excluded needs-triage because the issue is specific and well-scoped

Issue #44842

• Detected bug/fix language around schema validation and missing maxLength
• Included workflows because the affected files are workflow safe-output tool definitions used by the automation pipeline
• Added needs-triage conservatively because the report spans many tools and could merit maintainer refinement into more specific labels later

Label Distribution

View Label Statistics

• bug: 2 issues
• cli: 1 issue
• mcp: 1 issue
• security: 1 issue
• workflows: 1 issue
• needs-triage: 1 issue

Recommendations

• Consider tightening heuristics to avoid over-labeling long technical reports that contain mixed keywords from examples or repro steps.
• For MCP-related operational failures, favor mcp plus one primary type/component label over broad multi-label application.
• Review whether safe-output schema/tooling issues should also have a dedicated label for easier routing.

Confidence Assessment

• Overall Success: Medium
• Human Review Needed: 1 issue flagged with needs-triage
• Next Steps: Maintainers can refine component labeling for schema/tool-definition issues if a more specific label exists.

References:

• §29133696263

Generated by 🔧 Auto-Triage Issues · 7.12 AIC · ⌖ 12 AIC · ⊞ 4.1K · ◷

• expires on Jul 11, 2026, 5:03 PM UTC-08:00

[github-actions[bot]]

This discussion has been marked as outdated by Auto-Triage Issues.

A newer discussion is available at Discussion #45026.