Individual skill

directory-build-organization

USE ONLY for (1) two or more projects with repeated MSBuild policy, targets, or package versions, or (2) an existing Directory.Build.props/targets/rsp hierarchy with an import, placement, or layering defect. A one-project repo without an existing Directory.Build file is outside scope; do not load this skill. Covers centralizing shared policy and targets, Directory.Packages.props across projects, parent hierarchy/import structure, props-versus-targets placement, and folder/project exceptions. An existing hierarchy defect remains in scope when only one project is affected. For property value or condition semantics use property-patterns. Exclude legacy-to-SDK migration and non-MSBuild systems.

plugins/dotnet-msbuild/skills/directory-build-organization/SKILL.md

Read pinned source

Source commit 281e39451fb4487b4828d62fcb51ca853589a185

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
5,859
Repository last updated
Nov 8, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Organizing Build Infrastructure with Directory.Build Files

## Intent control

- For "should we", "how should we organize", "recommend", "advise", or review
  requests, inspect the actual project files and return a proposed layout only.
  Do not create or edit files unless the user explicitly asks to apply, move,
  centralize, or clean up the configuration.
- Before summarizing, verify which project retains each project-specific
  property, item, or target. Name the actual file; do not infer it from sibling
  names.
- Recommend a verification command only after discovering a real `.sln`,
  `.slnx`, `.proj`, or project file at that path. If no repo-root entry point
  exists, give commands for the discovered projects or state that the entry