incremental-build

Analyze MSBuild binlogs to diagnose slow incremental builds and suggest fixes.

Updated May 28, 2026
One-click install
npx skills add https://github.com/ojrojas/AgentsInstructions --skill incremental-build-ojrojas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incremental-build
Source: https://github.com/ojrojas/AgentsInstructions/tree/main/.claude/skills/dotnet-msbuild/skills/incremental-build
Command: npx skills add https://github.com/ojrojas/AgentsInstructions --skill incremental-build-ojrojas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps identify and resolve issues causing slow incremental builds in MSBuild, enabling faster subsequent build runs.

Core Features & Use Cases

  • Diagnose Slow Builds: Identifies common causes of slow incremental builds, such as missing Inputs/Outputs, volatile properties, and file writes outside tracked Outputs.
  • Binlog Analysis: Utilizes binary logs to diagnose why targets ran instead of being skipped.
  • Incremental Build Optimization: Provides guidance on making custom targets incremental and avoiding common mistakes.

Quick Start

Run the 'incremental-build' skill to analyze your MSBuild binlog and optimize your incremental builds.

Frequently Asked Questions about incremental-build

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my MSBuild incremental build run targets instead of skipping them?

MSBuild incremental builds run unnecessary targets due to missing Inputs/Outputs, volatile properties, or file writes outside tracked Outputs. Analyzing your binary logs helps diagnose exactly why targets execute instead of being skipped.

How do I diagnose slow .NET incremental builds using binlog analysis?

Diagnose slow .NET incremental builds by analyzing MSBuild binlogs to identify why specific targets ran. This process reveals common issues like missing Inputs/Outputs and volatile properties to optimize subsequent build runs.

What is the best way to make custom MSBuild targets incremental?

The best way to make custom MSBuild targets incremental is to define precise Inputs and Outputs. Avoiding common mistakes like volatile properties and untracked file writes ensures targets are skipped when outputs remain unchanged.

Do I need MSBuild binlog files to optimize my .NET incremental build?

Yes, you need MSBuild binlog files to optimize incremental builds. Binary logs provide the detailed execution trace required to diagnose why targets ran and identify specific bottlenecks in your .NET development workflow.

What causes slow incremental builds in .NET even when code hasn't changed?

Slow incremental builds in .NET occur when targets execute due to missing Inputs/Outputs definitions, volatile properties changing between runs, or file writes occurring outside tracked Outputs, forcing MSBuild to rebuild unnecessarily.