build-ci
Build scripts, CI pipelines, and versioning for the .NET 8 WPF widget host app. Use when setting up build workflows, CI checks, packaging gates, or semantic versioning rules.
When & Why to Use This Skill
This Claude skill automates the build, testing, and versioning lifecycle specifically for .NET 8 WPF applications. It enables developers to establish robust CI/CD pipelines with deterministic build scripts, integrated quality gates, and standardized semantic versioning to ensure high-quality, consistent software delivery and release management.
Use Cases
- Automating Build Workflows: Streamline the restore, build, and packaging process for .NET 8 WPF applications to ensure environment consistency and reduce manual errors.
- Implementing Quality Gates: Enforce mandatory testing and security scanning within CI pipelines to catch regressions and vulnerabilities before they reach production branches.
- Semantic Versioning Management: Automatically apply versioning rules and manage git tags to maintain a clear, traceable history of software releases and artifacts.
- Local-CI Parity: Develop and maintain PowerShell-based build scripts that function identically on local developer machines and CI servers, simplifying the debugging of build failures.
| name | build-ci |
|---|---|
| description | Build scripts, CI pipelines, and versioning for the .NET 8 WPF widget host app. Use when setting up build workflows, CI checks, packaging gates, or semantic versioning rules. |
Build CI
Overview
Automate builds, tests, and versioning for consistent releases.
This skill also defines “quality gates” expectations typically enforced in CI.
Workflow
- Define build steps (restore, build, test, pack).
- Configure CI pipeline stages and caching.
- Add versioning strategy (semver, git tags).
- Publish artifacts to CI outputs.
Definition of done (DoD)
- Local build script parity is maintained (prefer using
build.ps1when applicable) - CI steps are deterministic (no environment-dependent behavior)
- Minimum gates exist for relevant changes: build + nearest tests
- Packaging/signing steps are separated from compile/test steps
Guidance
- Keep CI deterministic and fast.
- Fail on warnings for release branches.
- Store build scripts in repo for local parity.
Quality gates (recommended)
- Restore/build/test are separate and cacheable
- Test runs are scoped (run the nearest test project(s) when possible)
- Security/quality scanning is additive (warn first, then enforce)
References
references/pipelines.mdfor CI flow.references/versioning.mdfor version rules.references/build-scripts.mdfor local build scripts.