dotnet-mcaf-source-control

Codify source-control policies for .NET repositories with branch rules and commit hygiene.

8|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-mcaf-source-control-postpartum-genushyacinthus29
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-mcaf-source-control
Source: https://github.com/Postpartum-genushyacinthus29/dotnet-skills/tree/main/skills/dotnet-mcaf-source-control
Command: npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-mcaf-source-control-postpartum-genushyacinthus29

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill codifies and enforces a robust source-control policy for .NET repositories, aligning teams on structure, branch naming, merge rules, commit hygiene, and secrets handling.

Core Features & Use Cases

  • Produce explicit governance artifacts (branching policy, PR guidelines, release strategy) and update in-repo docs to reflect agreed practices.
  • Enforce consistent naming and merge strategies across multiple repositories, reducing ambiguity and review effort.
  • Provide a repeatable workflow for policy application, validation, and governance reviews.

Quick Start

Run this skill to bootstrap repository governance by applying the policy and updating in-repo docs.

Frequently Asked Questions about dotnet-mcaf-source-control

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

FAQPage Schema
How do I enforce source-control governance policies across multiple .NET repositories?

Source-control governance is enforced by codifying branch rules, merge strategy, commit hygiene, and secrets handling into explicit artifacts. This skill applies consistent naming and validation guardrails across repositories to reduce ambiguity and review effort.

What is the best way to document branch naming and release strategy policies in a .NET repo?

Documenting branch and release policies involves producing explicit governance artifacts and updating in-repo docs to reflect agreed practices. This skill generates policy language, validation steps, and guardrails during repo bootstrap or PR-flow tightening.

How do I set up a pull request validation workflow for commit hygiene and secrets handling?

Pull request validation for commit hygiene and secrets handling requires evaluating changes against explicit governance criteria. This skill provides a repeatable workflow for policy application, validation, and governance reviews during the PR flow.

Do I need repository access to apply source-control policies and governance rules?

Repository access is required to apply source-control policies and evaluate changes against governance criteria. The skill operates during repo bootstrap and PR-flow tightening, requiring direct repository integration to produce governance artifacts.

Can I use this source-control policy skill for repo bootstrap and ongoing governance reviews?

Source-control policy skills for repo bootstrap and governance reviews are supported through a repeatable workflow. It codifies branching, merge rules, and commit hygiene, providing policy language and validation steps for both initial setup and continuous review.