skills.rest
patrikborosch
patrikboroschCOMMUNITY
Explore all skills by this author →
GitHub

release-public

Automate public release workflows for the skills-for-fabric repository.

14|3|Updated Mar 13, 2026
Search Tags:#release automation#copilot cli#smoke testing#public release#fabric skills#skills-for-fabric
One-click install
npx skills add https://github.com/patrikborosch/AnalyticsPlatformAgents --skill release-public
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-public
Source: https://github.com/patrikborosch/AnalyticsPlatformAgents/tree/main/creator/.github/skills/release-public
Command: npx skills add https://github.com/patrikborosch/AnalyticsPlatformAgents --skill release-public

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cutting public releases for the skills-for-fabric repository involves repetitive, error-prone steps including version stamping across multiple manifests, scrubbing internal references for public visibility, and verifying release artifacts work correctly in clean Copilot CLI installs. This skill eliminates manual errors and streamlines the entire release process.

Core Features & Use Cases

  • Automated Version Consistency: Stamps and validates version numbers across package.json, all plugin manifests, and marketplace files to prevent mismatched releases.
  • Public PR Automation: Creates release branches, scrubs internal repository references, and opens pull requests against the public microsoft/skills-for-fabric repository.
  • 3-Layer Smoke Testing: Runs structural, install, and behavioral verification to catch broken references, missing skills, and incorrect Copilot routing before merge.
  • Use Case: For teams maintaining public Fabric skill repositories, this skill reduces release time from hours of manual work to a single guided workflow, while preventing broken releases from human error.

Quick Start

Use the release-public skill to cut, verify, and publish a new 0.4.0 public release of the skills-for-fabric repository.

Frequently Asked Questions about release-public

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

FAQPage Schema
How do I automate a public release for Microsoft Fabric skill bundles?▼

You can automate a public release for Microsoft Fabric skill bundles by using an end-to-end workflow that eliminates manual version stamping and public PR creation. It guides the entire process from cutting the release to verifying Copilot CLI behavioral routing.

How does cross-manifest version consistency checking work for Fabric skills?▼

Cross-manifest version consistency checking works by automatically stamping and validating version numbers across package.json, plugin manifests, and marketplace files. This prevents mismatched releases by ensuring all configuration files reference the exact same release version.

What is the best way to scrub internal references before creating a public Fabric skills PR?▼

The best way to scrub internal references for a public Fabric skills PR is to automate the process during branch creation. The workflow removes internal repository references to ensure clean public visibility before opening a pull request against the public repository.

Can I run smoke tests for Copilot CLI behavioral routing before merging a Fabric release?▼

Yes, you can run a 3-layer smoke testing process that includes structural, install, and behavioral verification. This catches incorrect Copilot routing, broken references, and missing skills before you merge the public release PR.

Does the public release workflow support clean Copilot CLI install validation?▼

Yes, the public release workflow supports clean Copilot CLI install validation as part of its smoke testing layer. It verifies that release artifacts work correctly in fresh Copilot CLI environments to prevent broken public releases.

Why do Fabric marketplace mismatches occur during manual releases and how can I prevent them?▼

Fabric marketplace mismatches occur during manual releases due to human error in version stamping across multiple files. You can prevent them by using an automated release workflow with built-in guardrails that validates cross-manifest consistency.

Related Skills

Explore More Software Engineering Skills→
patrikboroschpatrikborosch
14

check-updates

Compare installed skills-for-fabric versions against the latest GitHub release.

Community
Intermediate
rritecrritec
3

check-updates

Compare local plugin versions against the latest marketplace release.

Community
Advanced
Extremez-SuryaExtremez-Surya

release

Automate the release process for vercel-plugin with gates, version bump, artifacts, commit, and push.

Community
Advanced
web-infra-devweb-infra-dev
1.1k

release-rsdoctor

Automate Rsdoctor package releases with version bumps, branches, and pull requests.

Official
Intermediate