build
Smart .NET build with fuzzy project matching and optional --fix for MCP-driven error resolution
What this skill does
# /dotnet:build Smart build command with fuzzy project/solution matching and optional automatic error fixing via MCP research. ## Arguments Parse arguments from `$ARGUMENTS`: | Flag | Description | Default | |------|-------------|---------| | `--solution <path>` | Target solution (supports fuzzy/partial matching) | Auto-detect | | `--project <path>` | Target project (supports fuzzy/partial matching) | None | | `--configuration <config>` | Build configuration | Debug | | `--fix` | Automatically fix errors using build-fixer agent | false | | `--verbosity <level>` | MSBuild verbosity (q, m, n, d, diag) | minimal | | `--no-restore` | Skip restore step | false | ## Workflow ### Step 1: Locate Target If `--project` specified: 1. Use Glob to find matching `.csproj` files 2. If partial name (e.g., "Api"), match against `*Api*.csproj` 3. If multiple matches, use AskUserQuestion to clarify 4. If natural language (e.g., "the API project"), use Grep to search project files for context If `--solution` specified: 1. Use Glob to find matching `.sln` files 2. Same fuzzy matching logic as projects If neither specified: 1. Look for `.sln` file in current directory or parent directories 2. If multiple solutions found, use AskUserQuestion to select 3. If no solution, look for single `.csproj` ### Step 2: Run Build Construct and execute build command: ```bash dotnet build "<target>" --configuration <config> --verbosity <verbosity> [--no-restore] ``` Capture both stdout and stderr for error analysis. ### Step 3: Analyze Results If build succeeds: - Report success with build time and output location - List any warnings (grouped by category if many) If build fails and `--fix` NOT specified: - Report errors clearly - Group errors by type (CS*, MSB*, NU*) - Suggest running with `--fix` flag If build fails and `--fix` IS specified: - Parse error codes from output - Extract relevant context (file, line, error message) - Spawn `build-fixer` agent with error context: ```text Task(dotnet:build-fixer, "Fix the following build errors: Errors: <paste parsed errors with file paths and line numbers> Project/Solution: <target> Configuration: <config> Research each error via MCP, apply fixes, and report what was changed.") ``` ### Step 4: Retry After Fix (if --fix) After build-fixer agent completes: 1. Run build again 2. If still errors, retry up to 3 times total 3. Report final status with list of fixes applied ## Output Format **Success:** ```text Build succeeded for <target> Configuration: <config> Time: <duration> Output: <path> Warnings: <count> (use --verbosity detailed to see) ``` **Failure (no --fix):** ```text Build failed for <target> Errors (grouped by type): CS1061: 3 errors - Member does not exist CS0103: 2 errors - Name does not exist in context Run with --fix to attempt automatic resolution. ``` **Failure (with --fix):** ```text Build failed for <target> Attempting automatic fix... - Fixed CS1061 in Foo.cs:42 (added missing using) - Fixed CS0103 in Bar.cs:15 (corrected typo) Retrying build... Build succeeded after 2 fix iterations. ``` ## Examples ```bash # Build solution in current directory /dotnet:build # Build specific project with fuzzy matching /dotnet:build --project Api # Build with automatic error fixing /dotnet:build --fix # Build Release configuration with detailed output /dotnet:build --configuration Release --verbosity detailed # Build specific solution /dotnet:build --solution MyApp.sln ```
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.