メニュー
Reviews dotnet/perf-autofiling-issues and lists issues that represent WASM Mono or WASM CoreCLR regressions. Use when preparing for perf triage, scanning auto-filed performance regressions, or generating a quick browser-WASM issue report.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | wasm-regression-triage |
| description | Reviews dotnet/perf-autofiling-issues and lists issues that represent WASM Mono or WASM CoreCLR regressions. Use when preparing for perf triage, scanning auto-filed performance regressions, or generating a quick browser-WASM issue report. |
This skill prepares a concise report of current auto-filed performance issues for browser WASM runtimes.
dotnet/perf-autofiling-issuesUse this skill only for the GitHub repository:
dotnet/perf-autofiling-issuesThe goal is to identify issues that are:
Do not include improvements or unrelated runtime issues.
Start with targeted GitHub issue search rather than listing the entire repository.
Prefer github-mcp-server-search_issues with repo-scoped queries such as:
repo:dotnet/perf-autofiling-issues is:issue is:open (wasm OR webassembly) regressionrepo:dotnet/perf-autofiling-issues is:issue is:open "CompilationMode:wasm"repo:dotnet/perf-autofiling-issues is:issue is:open (wasm OR webassembly) (mono OR coreclr)If the user asks for a broader view, include recently closed issues too by removing is:open.
For shortlisted issues, inspect the body with github-mcp-server-issue_read.
Keep the issue only if the content shows one or more of these signals:
Wasm: trueCompilationMode:wasmRuntimeMoniker: wasmmono, wasm-mono, coreclr, wasm-coreclr, or browser WASM runtime detailsExclude issues that are:
Group each matching issue into one of these buckets:
If the issue is clearly WASM-related but does not say whether it is Mono or CoreCLR, do not include it unless the user explicitly asks for all WASM regressions.
Return a compact Markdown report with:
Use the structure from the report template.
If no issues match, say:
No open WASM Mono or WASM CoreCLR regression issues were found in dotnet/perf-autofiling-issues.
User Request: "List the current WASM mono/coreclr regressions from perf-autofiling-issues."
Expected Behavior:
Output Example:
# WASM Regression Triage Report
Source: `dotnet/perf-autofiling-issues`
## WASM Mono
- #12345 - [Perf] Linux/x64: 5 Regressions ...
Link: https://github.com/dotnet/perf-autofiling-issues/issues/12345
Match: `Wasm: true`, `mono`, regression issue
## WASM CoreCLR
- #12346 - [Perf] Browser/wasm: 3 Regressions ...
Link: https://github.com/dotnet/perf-autofiling-issues/issues/12346
Match: `CompilationMode:wasm`, `coreclr`, regression issue
Problem: A search returns many unrelated perf issues.
Solution: Tighten the query with repo:dotnet/perf-autofiling-issues, is:open, regression, and wasm OR webassembly, then confirm the remaining candidates with issue_read.
Problem: The issue appears to be WASM-related but does not clearly say Mono or CoreCLR.
Solution: Exclude it from this report unless the user explicitly asks for all WASM regressions, not just Mono/CoreCLR.
Analyze CI build and test status from Azure DevOps and Helix for dotnet repository PRs. Use when checking CI status, investigating failures, determining if a PR is ready to merge, or given URLs containing dev.azure.com or helix.dot.net. Also use when asked "why is CI red", "test failures", "retry CI", "rerun tests", "is CI green", "build failed", "checks failing", or "flaky tests".
A meta-skill for managing Agent Skills. Use when creating, editing, modifying, updating, deleting, or refactoring skills. Also triggers for SKILL.md files, ~/.copilot/skills/ directory, .github/skills/ folder, skill frontmatter, skill instructions, skill templates, or any file changes in a skills directory. Ensures all changes are committed and pushed to git.
Analyze VMR codeflow PR status for dotnet repositories. Use when investigating stale codeflow PRs, checking if fixes have flowed through the VMR pipeline, debugging dependency update issues in PRs authored by dotnet-maestro[bot], checking overall flow status for a repo, or diagnosing why backflow PRs are missing or blocked.
Squashes multiple git commits into a single commit with a clean message. Use when cleaning up commit history, combining WIP commits, preparing branches for merge, tidying feature branches, or when asked to squash, combine, or consolidate commits.
Performs comprehensive code reviews for GitHub pull requests. Use when reviewing PRs, checking if a PR fixes an issue, analyzing code changes, or when given a GitHub PR URL (github.com/.../pull/...). Evaluates problem alignment, code quality, security threats, alternative approaches, edge cases, and identifies duplicate/existing implementations.