Standardize bootstrap blocks across dotnet skills

Author: KSemenenko

skills/mcaf-dotnet-analyzer-config/SKILL.md

@@ -48,6 +48,19 @@ compatibility: "Requires a .NET SDK-based repository; respects the repo's `AGENT
 5. Keep bulk switches such as `EnableNETAnalyzers` in MSBuild files, not in `.editorconfig`.
 6. Treat `.globalconfig` as an exceptional case, not the normal repo setup.
 
+## Bootstrap When Missing
+
+If analyzer configuration is requested but not structured yet:
+
+1. Detect current state:
+   - `rg --files -g '.editorconfig' -g '.globalconfig'`
+   - `rg -n "EnableNETAnalyzers|AnalysisLevel|AnalysisMode" -g '*.csproj' -g 'Directory.Build.*' .`
+2. Create or normalize one repo-root `.editorconfig` with `root = true`.
+3. Move rule severity into `.editorconfig` and keep bulk analyzer switches in project or MSBuild config.
+4. Add nested `.editorconfig` files only when a subtree really needs different scoped policy.
+5. Run `dotnet build <solution-or-project>` and return `status: configured` or `status: improved`.
+6. If the repo intentionally uses another documented analyzer-config ownership model, return `status: not_applicable`.
+
 ## Deliver
 
 - one explicit analyzer configuration ownership model

skills/mcaf-dotnet-features/SKILL.md

@@ -53,6 +53,19 @@ compatibility: "Requires a C# or .NET repository; respects explicit `LangVersion
    - `mcaf-solid-maintainability`
 8. After feature-driven refactors, run the repo's .NET quality pass through `mcaf-dotnet`.
 
+## Bootstrap When Missing
+
+If the requested C# feature depends on SDK or language support the repo does not have yet:
+
+1. Detect current state:
+   - `dotnet --list-sdks`
+   - `rg -n "<TargetFramework>|<LangVersion>|<TargetFrameworks>" -g '*.csproj' -g 'Directory.Build.*' .`
+2. Confirm whether the repo wants to stay on the current stable language level or intentionally upgrade.
+3. If the feature requires a newer supported SDK or target framework, upgrade the repo toolchain deliberately instead of relying on the local machine by accident.
+4. If the repo needs explicit `LangVersion`, record it in project or shared MSBuild config.
+5. Run `dotnet build <solution-or-project>` after the feature or toolchain change and return `status: configured` or `status: improved`.
+6. If the repo intentionally stays below the required language level, return `status: not_applicable`.
+
 ## Deliver
 
 - modern C# code that fits the repo's real language version

skills/mcaf-dotnet-quality-ci/SKILL.md

@@ -82,7 +82,7 @@ compatibility: "Requires a .NET solution or project; may update `AGENTS.md`, CI
    - architecture/security skills such as `mcaf-dotnet-netarchtest`, `mcaf-dotnet-archunitnet`, `mcaf-dotnet-codeql`, and `mcaf-dotnet-semgrep`
 8. Avoid overlapping tools with conflicting ownership. If you add an opinionated formatter, define whether it replaces or complements `dotnet format`.
 
-## Bootstrap When A Gate Is Missing
+## Bootstrap When Missing
 
 If a quality gate is requested but not configured, use this activation path:
 

skills/mcaf-dotnet/SKILL.md

@@ -71,7 +71,7 @@ compatibility: "Requires a .NET solution or project; respects root and local `AG
 7. If the repo does not define these commands clearly, tighten `AGENTS.md` before continuing so later agents stop guessing.
 8. Do not introduce preview language features unless the repo explicitly opts into preview in project or MSBuild settings.
 
-## Bootstrap Policy For Inactive Tools
+## Bootstrap When Missing
 
 When a requested .NET gate or tool is missing in this repo, do not stop at "not configured":