Güvenlik uyarılı skill

Bu skill destructive command içerebilir. Skill detaylarını ve kaynak içeriği incelemeden kurulum yapmayın, kopyalamayın, indirmeyin veya çalıştırmayın. Bilinçli ve kontrollü şekilde kullanın.

Tarayıcı bulguları

highprompt_injection

View source repo ↗

Issue Triage

dotnet/runtime/.github/skills/issue-triage

Çoklu dosya

.NET· v1.0.0

codingResmi

Resmi Sağlayıcı Skill'iView repo

Triage a dotnet/runtime GitHub issue with duplicate search, label check, reproduction, and ecosystem research, then recommend KEEP/CLOSE/NEEDS INFO. Use when asked to triage, evaluate, assess, or check a specific GitHub issue. Also use when asked "is this a duplicate", "should we close this", "check this issue", "what do you think about this issue", or when given a dotnet/runtime issue URL or number and asked for an opinion. Handles bug reports, API proposals, enhancements, performance regressio

Dosyalar11 dosya

SKILL.md488 satır

Loading editor…

Kurulum

Önerilen

Tek komut — ajanınız otomatik olarak devreye alır.

AI aracını seç

Kurulum komutunu görmek için yukarıdan bir AI aracı seçin.

veya

Manuel Kurulum

Daha fazla adım

Arşivi indirin ve dosyaları projenize manuel olarak ekleyin.

Skill detayları

Versiyonv1.0.0

Yazar.NET

Kategoricoding

Skill IDdotnet/runtime/.github/skills/issue-triage

Dosyalar11 dosya

İlgili skill'ler

Add New Jit Ee ApiAdd a new API to the JIT-VM (aka JIT-EE) interface in the codebase.Api ProposalCreate prototype-backed API proposals for dotnet/runtime. Use when asked to draft an API proposal, write an api-suggestion issue, refine a vague API idea into a complete proposal, or improve a proposal marked api-needs-work. Covers the full pipeline from research through prototyping, ref source generation, and publishing. DO NOT USE FOR bug fixes, code review, performance benchmarking, or internal API changes that don't affect public surface area.Aspnet BenchmarkRun the TechEmpower ASP.NET Core benchmarks against a locally-built dotnet/runtime, either locally with an SDK overlay or on external infrastructure using Crank, to validate the end-to-end impact of a runtime change (e.g. sockets, io_uring, GC, JIT) under realistic HTTP load. Use this when asked to benchmark, load-test, or profile an ASP.NET Core / Kestrel scenario, or to compare an env-var-gated feature (e.g. `DOTNET_USE_IO_URING`) end-to-end.Breaking Change DocGenerate breaking change documentation for merged dotnet/runtime PRs. USE FOR: creating breaking change docs, "document this breaking change", "write breaking change issue for PR #NNNNN", processing PRs labeled needs-breaking-change-doc-created. DO NOT USE FOR: general code review (use code-review skill), bug fixes, API proposals (use api-proposal skill).Build And TestBuild and test dotnet/runtime locally. Covers the mandatory baseline build, per-component build and test commands, Windows/PowerShell equivalents, running individual tests, and troubleshooting. USE FOR: any build or test invocation in this repo, and before making code changes under CCA. DO NOT USE FOR: CI pipeline triage (use ci-pipeline-monitor) or benchmarking (use microbenchmark for method/API-level measurements or aspnet-benchmark for end-to-end ASP.NET Core/HTTP load testing).Ci Pipeline MonitorMonitors .NET runtime CI test pipelines on Azure DevOps. Use this skill when asked to monitor CI pipeline test results, triage CI test failures across ADO pipelines, or generate CI test monitoring reports.