Diagnosa bottleneck evaluasi MSBuild dengan menganalisis pemrosesan file project, rantai import, dan biaya ekspansi glob sebelum target dijalankan.
- Bintang GitHub
- 5.942
- File
- 1
- Commit terakhir
- 11 Nov 2026
- Lisensi
- MIT
- Tool yang diizinkan
- —
Apa fungsi skill eval-performance?
Diagnosa bottleneck evaluasi MSBuild dengan menganalisis pemrosesan file project, rantai import, dan biaya ekspansi glob sebelum target dijalankan.
Ringkasan dibuat dari SKILL.md skill ini.
Tentang skill eval-performance
Mengidentifikasi bottleneck evaluasi MSBuild sebelum target apa pun dijalankan adalah kemampuan yang diberikan skill ini bagi developer yang mengelola sistem build kompleks. Skill ini berfokus pada fase di mana MSBuild membaca file project, memproses import, dan melakukan ekspansi glob, yang dapat menyebabkan proses build awal menjadi lambat meskipun tidak ada kompilasi yang diperlukan. Tool ini ditujukan bagi pengguna yang memiliki bukti terukur bahwa evaluasi adalah sumber utama kelambatan, bukan karena eksekusi target atau masalah incremental rebuild.
Seorang agent harus memuat skill ini ketika binlog atau ringkasan performa menunjukkan biaya tinggi selama fase pemrosesan project awal. Skill ini mengandalkan binlog MCP server untuk mencantumkan durasi evaluasi, memeriksa global properties, dan menganalisis kedalaman rantai import. Skill ini juga menggunakan teknik preprocessing untuk memeriksa file project yang telah diekspansi dan mengidentifikasi pola glob yang mahal, seperti yang menelusuri direktori node_modules atau .git. Dengan menganalisis metrik spesifik ini, skill ini membantu menentukan apakah rantai import yang dalam, evaluasi redundan di bawah global properties yang berbeda, atau fungsi property dengan file-I/O yang berat adalah penyebabnya.
Apa yang bisa dilakukan agent dengannya
- 1Analisis kedalaman rantai importTentukan apakah sebuah project memiliki hierarki import yang terlalu dalam sehingga memperlambat awal proses build.
- 2Deteksi evaluasi project yang redundanPeriksa apakah sebuah project dievaluasi berkali-kali akibat perbedaan global properties.
- 3Inspeksi biaya fungsi propertyPeriksa fungsi property yang melakukan file-I/O berat selama fase evaluasi.
Ditulis dari SKILL.md milik skill tersebut. Setiap use case diverifikasi dengan kutipan darinya.
Cara install skill eval-performance
Setiap perintah menyalin folder skill ke direktori skills client. Restart client atau mulai sesi baru untuk memuatnya.Install skill eval-performance di Plugin
/plugin marketplace add dotnet/skills /plugin install dotnet-msbuild@dotnet-agent-skills
Install skill eval-performance di Claude Code
~/.claude/skills/eval-performance/SKILL.md
$ npx degit dotnet/skills/plugins/dotnet-msbuild/skills/eval-performance ~/.claude/skills/eval-performanceInstall skill eval-performance di Claude Code (project)
.claude/skills/eval-performance/SKILL.md
$ npx degit dotnet/skills/plugins/dotnet-msbuild/skills/eval-performance .claude/skills/eval-performanceInstall skill eval-performance di Codex
~/.agents/skills/eval-performance/SKILL.md
$ npx degit dotnet/skills/plugins/dotnet-msbuild/skills/eval-performance ~/.agents/skills/eval-performanceInstall skill eval-performance di Gemini CLI
~/.gemini/skills/eval-performance/SKILL.md
$ npx degit dotnet/skills/plugins/dotnet-msbuild/skills/eval-performance ~/.gemini/skills/eval-performanceInstall skill eval-performance di Claude.ai
npx degit dotnet/skills/plugins/dotnet-msbuild/skills/eval-performance eval-performance && zip -r eval-performance.zip eval-performance # claude.ai → Customize → Skills → + → Create skill → Upload a skill → eval-performance.zip
Pengecekan otomatis
Berjalan 15 Nov 2026Laporan lengkap →Lolos cek otomatis kami. Ini bukan audit keamanan: baca skripnya sebelum membiarkan agent menjalankannya. Cara kerja checks
- Source repository terhubung dan dapat dijangkaudotnet/skills/plugins/dotnet-msbuild/skills/eval-performance is public and reachablegithub.com/dotnet/skills/tree/HEAD/plugins/dotnet-msbuild/sk ↗Lolos
- Lisensi open source (OSI)MITspdx.org/licenses/MIT.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit 2026-11-11github.com/dotnet/skills/commits ↗Lolos
- Skrip tanpa unduh-lalu-jalankan atau pencurian kredensialNo scripts in the skill folderLolos
- Tidak ada instruksi tersembunyi di SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/dotnet/skills/blob/HEAD/plugins/dotnet-msbuild/sk ↗Lolos
- Tool yang diizinkan otomatis dibatasiNo pre-approved tools; the agent asks before using onegithub.com/dotnet/skills/blob/HEAD/plugins/dotnet-msbuild/sk ↗Lolos
- SKILL.md mengikuti format Agent SkillsValid name and description; says when to use it; 130 linesgithub.com/dotnet/skills/blob/HEAD/plugins/dotnet-msbuild/sk ↗Lolos
SKILL.md
Lihat di GitHubDiagnosing MSBuild Evaluation Performance
Evaluation is the work MSBuild does before any target runs — reading project files, processing imports, expanding globs. This skill helps you find and confirm evaluation bottlenecks. Measure first; recommend a change only when a measurement proves it is warranted.
Confirm the problem before changing anything
Engage only when evaluation is measurably the bottleneck. Do NOT act when:
- The slowness is during compilation or target execution, not evaluation.
That is not an evaluation problem — use
build-perf-diagnosticsinstead. - The complaint is "rebuilds too much" / incremental build. Use
incremental-buildinstead. - You have no measurement. If no binlog or timing summary shows evaluation is slow, gather one first (see below). Do not guess from reading project files.
- A pattern below appears but evaluation is already fast. Broad globs, deep
imports, or
EnableDefaultItemsare only worth flagging when the numbers show they cost real time. A project that evaluates quickly needs no change.
When a pattern is present but unmeasured, report it as an observation and let the user decide — do not rewrite working configuration to match a "best practice" without evidence it costs measurable evaluation time. Prefer the smallest, most targeted change; never disable SDK defaults as a first move.
MSBuild Evaluation Phases
For a comprehensive overview of MSBuild's evaluation and execution model, see Build process overview.
- Initial properties: environment variables, global properties, reserved properties
- Imports and property evaluation: process
<Import>, evaluate<PropertyGroup>top-to-bottom - Item definition evaluation:
<ItemDefinitionGroup>metadata defaults - Item evaluation:
<ItemGroup>withInclude,Remove,Update, glob expansion - UsingTask evaluation: register custom tasks
Key insight: evaluation happens BEFORE any targets run. Slow evaluation = slow build start even when nothing needs compiling.
Diagnosing Evaluation Performance
Primary: binlog MCP (preferred)
Use the binlog MCP server (Microsoft.AITools.BinlogMcp, exposed under the binlog MCP namespace) to analyze evaluation performance:
- Use the evaluations tool to list all evaluations and their durations
- Use evaluation_global_properties to check for multiple evaluations with differing global properties
- Use evaluation_properties to inspect evaluated properties for a specific project+TFM
- Use imports tool to analyze the import chain depth and structure
- Use properties tool to check for expensive property function evaluations
Fallback: text-log replay and preprocessing (when MCP is unavailable)
Using binlog
- Replay the binlog:
dotnet msbuild build.binlog -noconlog -fl "-flp:v=diag;logfile=full.log" - Search for evaluation events:
grep -i 'Evaluation started\|Evaluation finished' full.log - Multiple evaluations for the same project = overbuilding
- Look for "Project evaluation started/finished" messages and their timestamps
Using /pp (preprocess)
dotnet msbuild -pp:full.xml MyProject.csproj- Shows the fully expanded project with ALL imports inlined
- Use to understand: what's imported, import depth, total content volume
- Large preprocessed output (>10K lines) = heavy evaluation
Using /clp:PerformanceSummary
- Add to build command for timing breakdown
- Shows evaluation time separately from target/task execution
Expensive Glob Patterns
Only pursue these remedies once a measurement shows item evaluation is slow and the globs are the cause; a custom glob that isn't walking large trees is fine.
- Globs like
**/*.cswalk the entire directory tree - Default SDK globs are optimized, but custom globs may not be
- Problem: globbing over
node_modules/,.git/,bin/,obj/— millions of files - Remedy: use
<DefaultItemExcludes>to exclude large directories - Remedy: be specific with glob paths:
src/**/*.csinstead of**/*.cs - Remedy: use
<EnableDefaultItems>false</EnableDefaultItems>only as a last resort (loses SDK defaults) — prefer the two options above first - Check: grep for Compile items in the diagnostic log → if Compile items include unexpected files, globs are too broad
Import Chain Analysis
- Deep import chains (>20 levels) slow evaluation
- Each import: file I/O + parse + evaluate
- Common causes: NuGet packages adding .props/.targets, framework SDK imports, Directory.Build chains
- Diagnosis:
/ppoutput → search for<!-- Importingcomments to see import tree - Remedy (only if the chain is measurably costly): reduce transitive package imports where possible, consolidate imports
Multiple Evaluations
- A project evaluated multiple times = wasted work
- Common causes: referenced from multiple other projects with different global properties
- Each unique set of global properties = separate evaluation
- Diagnosis:
grep 'Evaluation started.*ProjectName' full.log→ if count > 1, check for differing global properties - Fix: normalize global properties, use graph build (
/graph)
TreatAsLocalProperty
- Prevents property values from flowing to child projects via MSBuild task
- Overuse: declaring many TreatAsLocalProperty entries adds evaluation overhead
- Correct use: only when you genuinely need to override an inherited property
Property Function Cost
- Property functions execute during evaluation
- Most are cheap (string operations)
- Expensive:
$([System.IO.File]::ReadAllText(...))during evaluation — reads file on every evaluation - Expensive: network calls, heavy computation
- Rule: property functions should be fast and side-effect-free
Optimization Checklist
- Check preprocessed output size:
dotnet msbuild -pp:full.xml - Verify evaluation count: should be 1 per project per TFM
- Exclude large directories from globs
- Avoid file I/O in property functions during evaluation
- Minimize import depth
- Use graph build to reduce redundant evaluations
- Check for unnecessary UsingTask declarations
Berkas dalam skill ini
1Pertanyaan seputar skill eval-performance
Bagaimana cara install skill eval-performance di Claude Code?
Jalankan npx degit dotnet/skills/plugins/dotnet-msbuild/skills/eval-performance ~/.claude/skills/eval-performance. Claude Code memuat skill dari ~/.claude/skills (semua proyek) atau .claude/skills (satu proyek) dan menggunakan skill saat deskripsinya cocok dengan tugas.
Client mana saja yang bisa menggunakan skill eval-performance?
Client apa pun yang membaca format Agent Skills: Claude Code, Codex, Gemini CLI, dan claude.ai (unggah sebagai ZIP). Script dalam skill hanya berjalan di client yang mengizinkan eksekusi kode.
Kapan saya harus menggunakan skill ini?
Gunakan skill ini untuk mendiagnosa pengulangan evaluasi di bawah varian global-property, glob yang mahal (seperti node_modules atau .git), rantai import yang dalam, atau file preprocessed yang besar. Jangan gunakan untuk bottleneck pada tahap eksekusi atau masalah incremental rebuild.