1.4K skills · sorted by relevance
Diagnose why MSBuild builds across multiple projects fail to run efficiently in parallel. Use build logs and project dependencies to identify blocking chains, then recommend changes to references, scheduling, or parallel execution settings.
Diagnose unnecessary rebuilds in MSBuild by examining build logs, file timestamps, and declared inputs and outputs. Identify why work repeats, guide fixes when requested, and verify that a second unchanged build skips the expected targets.
Investigate MSBuild failures, measure slow builds, or review existing build definitions. Use binary logs, project settings, and comparable timing measurements to identify causes, propose focused repairs, and verify behavior without broad configuration changes.
Establish repeatable performance measurements for MSBuild and .NET builds before optimizing. Compare clean-output, changed-source, and unchanged builds, record timing ranges, and assess output layouts, dependency references, and parallel build options against the measured baseline.
Investigate MSBuild failures caused by projects or build configurations writing to the same output folders. Compare build logs, output paths, and project settings to identify collisions behind overwritten files, restore errors, or failures that disappear on retry.
Fix false-positive Cloud Run deploys where `gcloud builds submit --tag` silently fails but the follow-up `gcloud run services update --image :latest` succeeds against a stale image, producing a confident "Deploying... Done" message with pre-fix code still live. Use when: (1) gcloud builds submit prints "ERROR: (gcloud.builds.submit) Invalid value for [source]: Dockerfile required when specifying --tag" but the shell scrolls past it, (2) code changes verified locally aren't visible in production after a deploy that printed "revision ... has been deployed and is serving 100 percent of traffic", (3) Chaining `gcloud builds submit` and `gcloud run services update` in a single copy-paste block, (4) Using the mutable `:latest` tag for Cloud Run deploys.
The English summary is being prepared. Showing the original description.
Add GraalVM Native Image support to Java applications to build native executables. The skill adapts Maven or Gradle configuration, fixes build errors iteratively, and checks application behavior, startup time, and memory use.
Creates and automates custom image builds with EC2 Image Builder - Linux, Windows, and macOS AMIs, and container images to ECR. Covers the build IAM role, Amazon-managed and custom components, image recipes, infrastructure and distribution configuration (launch templates, SSM parameters, other Regions), one-off builds, recurring scheduled pipelines for golden AMI automation and OS patching, custom image workflows, and diagnosing failed builds. Applies when creating, automating, or scheduling AMI or container image builds with Image Builder, or when debugging a failed build. Not for launching instances from existing AMIs, AMI lifecycle/retirement, or general EC2 fleet management.
The English summary is being prepared. Showing the original description.
Guide for optimizing MSBuild incremental builds. USE FOR: builds slower than expected on subsequent runs, 'nothing changed but it rebuilds anyway', diagnosing why targets re-execute unnecessarily, fixing broken no-op builds. Covers 8 common causes: missing Inputs/Outputs on custom targets, volatile properties in output paths (timestamps/GUIDs), file writes outside tracked Outputs, missing FileWrites registration, glob changes, Visual Studio Fast Up-to-Date Check (FUTDC) issues. Key diagnostic: look for 'Building target completely' vs 'Skipping target' in binlog. DO NOT USE FOR: first-time build slowness (use build-perf-baseline), parallelism issues (use build-parallelism), evaluation-phase slowness (use eval-performance), non-MSBuild build systems.
The English summary is being prepared. Showing the original description.
Use only for MSBuild failure investigation, build-performance analysis, or review of existing build XML/extension contracts. A plan to convert a working legacy/non-SDK project to SDK style or migrate packages.config is a project-system migration, NOT a build-file review: do not activate, even to check scope. Framework/API upgrades are also excluded. Activate for advisory Import/Exists hook and NuGet packed-import questions even without a checkout or failed build; .csproj/.fsproj/.vbproj/.props/.targets conditions; custom-target inputs/outputs; .binlog capture/replay; failing dotnet build/restore/pack/publish or MSBuild-based test builds; slow evaluation, compilation, copying, or no-change builds; and controlled timing comparisons. Exclude SDK installation alone, C# refactoring, runtime profiling, assertions after successful builds, and non-MSBuild builds.
The English summary is being prepared. Showing the original description.
Optimize Docker build times using layer caching, multi-stage builds, BuildKit features, and dependency-first copy patterns. Applicable to R, Node.js, and Python projects. Use when Docker builds are slow due to repeated package installations, when rebuilds reinstall all dependencies on every code change, when image sizes are unnecessarily large, or when CI/CD pipeline builds are a bottleneck.
The English summary is being prepared. Showing the original description.
Detects MSBuild projects with conflicting OutputPath or IntermediateOutputPath. Only activate in MSBuild/.NET build context. USE FOR: builds failing with 'Cannot create a file when that file already exists', 'The process cannot access the file because it is being used by another process', intermittent build failures that succeed on retry, missing outputs in multi-project builds, multi-targeting builds where project.assets.json conflicts. Diagnoses when multiple projects or TFMs write to the same bin/obj directories due to shared OutputPath, missing AppendTargetFrameworkToOutputPath, or extra global properties like PublishReadyToRun creating redundant evaluations. DO NOT USE FOR: file access errors unrelated to MSBuild (OS-level locking), single-project single-TFM builds, non-MSBuild build systems. INVOKES: binlog MCP server tools (overview, projects, evaluations, properties, double_writes); falls back to dotnet msbuild binlog replay + grep when the MCP is unavailable.
The English summary is being prepared. Showing the original description.
Guide for optimizing MSBuild incremental builds. Only activate in MSBuild/.NET build context. USE FOR: builds slower than expected on subsequent runs, 'nothing changed but it rebuilds anyway', diagnosing why targets re-execute unnecessarily, fixing broken no-op builds. Covers 8 common causes: missing Inputs/Outputs on custom targets, volatile properties in output paths (timestamps/GUIDs), file writes outside tracked Outputs, missing FileWrites registration, glob changes, Visual Studio Fast Up-to-Date Check (FUTDC) issues. Key diagnostic: look for 'Building target completely' vs 'Skipping target' in binlog. DO NOT USE FOR: first-time build slowness (use build-perf-baseline), parallelism issues (use build-parallelism), evaluation-phase slowness (use eval-performance), non-MSBuild build systems. INVOKES: binlog MCP server tools (overview, search, target details); falls back to dotnet build /bl, binlog replay with diagnostic verbosity.
The English summary is being prepared. Showing the original description.
Guide for using MSBuild Server to improve CLI build performance. Only activate in MSBuild/.NET build context. Activate when developers report slow incremental builds from the command line, or when CLI builds are noticeably slower than IDE builds. Covers MSBUILDUSESERVER=1 environment variable for persistent server-based caching. Do not activate for IDE-based builds (Visual Studio already uses a long-lived process).
The English summary is being prepared. Showing the original description.
Prepare Cline desktop releases for stable, beta, or nightly testing. Coordinate release notes, matching version files, tags, and a GitHub Actions workflow that builds signed installers and manages automatic update feeds for release channels.
Prepare and verify application deployments to Azure Container Apps using azd and Bicep. Review environment settings, remote builds, identity permissions, and deployment changes, then check running revisions, service health, and frontend-to-backend connections.
Keep a Mac awake during long builds, downloads, or supervised automation using the built-in caffeinate command. Set a duration or follow a running process, control display sleep, check whether it is active, and stop it early.
Set up and maintain a monorepo, a single repository containing multiple apps and packages. Use Turborepo, Nx, and pnpm workspaces to organize shared code, manage dependencies, improve builds, and plan package releases.
Configure Turborepo builds for projects containing multiple apps and shared packages. Set task dependencies, reuse saved build outputs locally or remotely, limit runs to affected packages, and investigate why cached results are not being reused.
Manage Azure DevOps projects, repositories, pull requests, pipelines, and work items through command-line tools. The skill guides authentication, resource operations, and automation scripts, with references for builds, permissions, packages, and common errors.
Manage multiple apps and shared packages in one repository. Analyze dependencies and change impacts, limit builds and tests to affected packages, configure caching, and plan repository consolidation while preserving Git history.
Roll back Kortix production to a previously released version using existing builds. Covers frontend and backend rollback, database compatibility checks, prevention of unintended frontend rebuilds, and returning to the latest version through a later release.
Create and run KubeSphere DevOps pipelines connected to Jenkins to automate builds and tests. Covers branch-specific workflows, required input parameters, private repository credentials, execution monitoring, logs, and downloading build output files.
Builds CARLA's ue4-dev branch on Linux, producing the Unreal Engine 4.26 editor, server modules, and an installed Python client package. Fetches required content, optionally compiles native ROS 2 support, and verifies the build against a source-built server.