publish-preflight

Automate pre-publish validation for NuGet releases with pass/fail readiness reports.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/darylmcd/Roslyn-Backed-MCP --skill publish-preflight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish-preflight
Source: https://github.com/darylmcd/Roslyn-Backed-MCP/tree/main/.claude/skills/publish-preflight
Command: npx skills add https://github.com/darylmcd/Roslyn-Backed-MCP --skill publish-preflight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-publish validation gates ensure NuGet releases are ready, preventing regressions and discovery of issues before publish by checking version drift, AI documentation alignment, and the full build/test/publish readiness across the repository.

Core Features & Use Cases

  • Version drift verification across release files
  • AI docs validation to ensure documentation stays current
  • Full release pipeline checks: build, test, and publish steps
  • CHANGELOG presence and version alignment
  • SECURITY.md supported versions consistency
  • Doc-audit freshness verification for consumer docs

Quick Start

Run the publish-preflight checks to ensure version drift, AI docs validity, build/test readiness, changelog presence, security policy alignment, and doc-audit freshness prior to release.

Frequently Asked Questions about publish-preflight

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

FAQPage Schema
How do I automate pre-publish validation checks for NuGet releases?

Automate pre-publish validation for NuGet releases by running comprehensive checks that verify version drift, build and test workflows, changelog presence, and security policy alignment before publishing.

What is version drift verification and why does it matter for package releases?

Version drift verification checks consistency across release files to prevent publishing outdated or misaligned package versions. It ensures all release artifacts reference the correct version before reaching consumers.

How do I check if my documentation is fresh before publishing a package release?

Check documentation freshness by validating AI docs alignment and running doc-audit verifications. These checks confirm consumer docs and AI-generated documentation stay current with code changes.

Can I use pre-publish checks across local validation scripts and CI-like environments?

Yes, pre-publish checks apply across CI-like environments, local validation scripts, and manual gates. They generate a final readiness report with pass or fail outcomes for repository maintainers.

Does pre-publish validation check SECURITY.md supported versions consistency?

Yes, pre-publish validation checks SECURITY.md supported versions consistency to ensure your security policy aligns with the actual release versions being published.

What does a pre-publish readiness report include for NuGet package releases?

A pre-publish readiness report includes pass or fail outcomes for version drift, AI docs validity, build and test readiness, changelog presence, security policy alignment, and doc-audit freshness.