ops-rebuild-clean

To ensure a clean build state and resolve transient compilation issues, follow this process:

1. Stop Background Processes

   • Ensure no background dotnet processes are running that might lock files.
   • Check for running Aspire instances or test hosts.

2. Clean Solution

   • Run dotnet clean in the root directory.
   • This removes all intermediate output and binaries.

// turbo 3. Rebuild

• Run dotnet build in the root directory to compile the entire solution from scratch.

4. Verify and Report
   • Check the output for any persistent errors.
   • If the build succeeds, notify the user: "✅ Workspace is clean and builds successfully."
   • If errors persist, they are likely genuine code issues rather than stale artifacts.
   • Use grep_search or read_file to investigate the specific error messages.

When to Use

• Build errors that seem inconsistent
• After major dependency changes
• When switching branches with significant changes
• Stale artifact issues
• After package version updates

Related Skills

Used By:

• /test__verify_feature - May reference this for clean builds

Next Steps:

• /test__verify_feature - Full verification after clean rebuild
• /test__unit_suite or /test__integration_suite - Test the rebuilt solution

See Also:

• getting-started - Build instructions
• aspire-guide - Running the application