Automated summary
This skill uses Nuke Build for all .NET build, test, clean, and restore operations, avoiding raw dotnet commands.
Strengths
- Ensures consistent builds across local and CI environments
- Handles project dependencies and build ordering correctly
- Runs code generators and pre/post-build tasks
Limitations
- Requires Nuke to be installed and configured in the project
- Does not cover non-.NET projects
When you need to build, test, or clean a .NET project that uses Nuke Build.
For simple .NET projects without Nuke, where dotnet build is sufficient.
Security analysis
SafeThe skill only instructs running nuke build commands, which are standard build automation. No destructive, exfiltrative, or obfuscated actions are present.
No concerns found
How this analysis is madeExamples
Build the .NET solution using Nuke.Run all tests with Nuke.Clean and then rebuild the project using Nuke.name: build version: 0.1.0 kind: cli description: "Build, test, or compile the solution using Nuke. Use when asked to build, compile, run tests, clean, restore, or perform any .NET build operation." contracts: success: "Build completes successfully with zero errors" failure: "Build fails with compilation errors or missing dependencies"
Build Skill
This project uses Nuke Build for all build operations. Never use raw dotnet commands.
Command Reference
| Operation | Nuke Command | Do NOT Use |
|-----------|--------------|------------|
| Build | nuke compile | dotnet build |
| Test | nuke test | dotnet test |
| Clean | nuke clean | dotnet clean |
| Restore | nuke restore | dotnet restore |
| Pack | nuke pack | dotnet pack |
Common Workflows
Build the solution
nuke compile
Run all tests
nuke test
Clean and rebuild
nuke clean compile
List available targets
nuke --help
Why Nuke (Not dotnet)
- Ensures consistent build behavior across local and CI environments
- Handles project dependencies and build ordering correctly
- Runs code generators and pre/post-build tasks
- Provides reproducible builds with proper configuration
Instructions
When the user asks to build, test, compile, or perform any .NET build operation:
- Use the appropriate
nukecommand from the table above - Report build errors clearly from the output
- Never suggest
dotnet build,dotnet test, or other raw dotnet commands as alternatives - If a specific project needs building, check if there's a Nuke target for it first
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/build-with-nuke-build-mmk3ni6a/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/build-with-nuke-build-mmk3ni6a' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/build-with-nuke-build-mmk3ni6a/download' --output '.skill-downloads/build-with-nuke-build-mmk3ni6a/SKILL.md.part' && mv '.skill-downloads/build-with-nuke-build-mmk3ni6a/SKILL.md.part' '.skill-downloads/build-with-nuke-build-mmk3ni6a/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/build-with-nuke-build-mmk3ni6a/SKILL.md' && test -s '.skill-downloads/build-with-nuke-build-mmk3ni6a/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/build' && cp -R '.skill-downloads/build-with-nuke-build-mmk3ni6a' '.claude/skills/build'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/build-with-nuke-build-mmk3ni6a'openskills read 'build-with-nuke-build-mmk3ni6a'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/build-with-nuke-build-mmk3ni6a/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.