dotnet-pulse-ops

Run the DocSmith Pulse web app, apply EF Core migrations, and validate safety controls.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/habrahgithub/node-backend-starter --skill dotnet-pulse-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-pulse-ops
Source: https://github.com/habrahgithub/node-backend-starter/tree/main/.codex/skills/dotnet-pulse-ops
Command: npx skills add https://github.com/habrahgithub/node-backend-starter --skill dotnet-pulse-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Dotnet Pulse Ops Skill centralizes operational steps for the DocSmith.Pulse .NET solution so engineers can reliably run the web app, manage EF Core migrations, and validate safety controls without guessing project boundaries.

Core Features & Use Cases

  • Run and debug the web application using the repository dotnet wrapper and the Web startup project to reproduce and troubleshoot issues locally.
  • Apply and create EF Core migrations against the Infrastructure project with the Web project as the startup project to keep the database schema synchronized.
  • Safety and release validation including kill-switch checks, audit log append-only protections, and configuration guardrails to ensure safe deployments.

Quick Start

Start the DocSmith.Pulse web app using the repository SDK wrapper and apply pending EF Core migrations for the PulseDbContext.

Frequently Asked Questions about dotnet-pulse-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run EF Core migrations for a .NET 8 web app using a separate Infrastructure project?

To apply EF Core migrations for a .NET 8 web app, target the Infrastructure project containing the DbContext while setting the Web project as the startup project. This ensures the migration commands execute within the correct application configuration context.

What safety guardrails should I validate before deploying an ASP.NET Core application?

Validating safety guardrails before deploying an ASP.NET Core application involves checking the kill-switch, verifying append-only audit log protections, and enforcing configuration guardrails to ensure safe and controlled release behavior.

How do I manage the DocSmith Pulse .NET solution lifecycle for local debugging?

Manage the DocSmith Pulse .NET solution lifecycle for local debugging by using the repository SDK wrapper to run the Web startup project. This reproduces and troubleshoots issues locally within the projects/DocSmith.Pulse directory.

Do I need a specific .NET version to apply EF Core migrations safely?

You need .NET 8 to apply EF Core migrations safely within this workflow. The solution targets .NET 8 and uses EF Core, requiring the compatible SDK wrapper to execute migration and validation commands correctly.

What is the best way to keep database schemas synchronized across .NET projects?

The best way to keep database schemas synchronized across .NET projects is by creating and applying EF Core migrations against the Infrastructure project. This maintains schema alignment with the Web startup project's configuration.

Why does my EF Core migration fail when targeting multiple projects in a .NET solution?

EF Core migrations fail when project boundaries are incorrect. You must explicitly target the Infrastructure project for the PulseDbContext while setting the Web project as the startup to provide the proper runtime environment.