perf-autofiler-triage

To triage dotnet performance regression issues, this Skill parses auto-filed issues to extract benchmark names, regression ratios, and baseline/compare commits, categorizing them into infrastructure artifacts or real regressions. It generates a structured triage summary with data-gap checks for rapid remediation.

Automated performance regression analysis distinguishes infrastructure artifacts by parsing issue bodies and comments to extract configuration details and run metadata. It correlates these data points with dotnet/performance repo changes to identify whether the regression ratio indicates a real performance drop or an infrastructure anomaly.

The best way to extract benchmark names and regression ratios from perf-autofiling issues is to feed the issue body and comments into this analysis workflow. It automatically parses and structures the baseline commit, compare commit, and configuration fields into a comprehensive triage summary.

Yes, you can use this triage workflow for issues missing baseline or compare commit data because it includes built-in data-gap checks. The analysis identifies missing fields like baseline run or compare run metadata and flags them in the structured triage summary before categorization.

Your dotnet performance automation workflow needs a structured triage summary to enable rapid categorization by severity. It systematically extracts benchmark names and regression ratios, tracking correlations with repo changes to provide clear guidance for remediation and escalation workflows.

No specific dependencies or environment setup are required to use this performance analysis triage Skill. It operates directly on the text of auto-filed issues and comments from the dotnet/performance pipeline to extract fields and generate the structured triage output.