mcaf-source-control

Define repository source-control policies for branching, merging, and commit hygiene.

4|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/managedcode/MCPGateway --skill mcaf-source-control
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcaf-source-control
Source: https://github.com/managedcode/MCPGateway/tree/main/.codex/skills/mcaf-source-control
Command: npx skills add https://github.com/managedcode/MCPGateway --skill mcaf-source-control

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill establishes and refines critical source control policies for repositories, ensuring consistency in structure, naming, merging, and commit hygiene, while also addressing security concerns like secrets in Git.

Core Features & Use Cases

  • Policy Definition: Clearly articulates rules for branching, merging, and release strategies.
  • Hygiene Enforcement: Promotes best practices for commit messages and secrets management.
  • Documentation: Updates contribution guidelines and repository policy files.
  • Use Case: When bootstrapping a new project, use this Skill to define a robust source control strategy that includes clear branch naming conventions, a defined merge process (e.g., squash commits), and a strict policy on handling secrets.

Quick Start

Use the mcaf-source-control skill to define branch naming and merge rules for this repository.

Frequently Asked Questions about mcaf-source-control

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

FAQPage Schema
How do I enforce git branch naming conventions and merge strategies?

Source control policies establish rules for repository structure, branch naming, merge strategies, and commit hygiene. They are needed when bootstrapping a new project or tightening pull request flows to ensure consistent contributions.

What is the best way to define commit hygiene and secrets-in-git discipline?

Defining commit hygiene and secrets-in-git discipline involves establishing rules for commit messages and strict policies on handling secrets. This skill refines these policies and updates contribution guidelines to enforce them.

How do I set up source control policies when bootstrapping a new repository?

Set up source control policies during repo bootstrapping by defining branch naming conventions, a defined merge process like squash commits, and a strict policy on handling secrets. This skill documents these policies in contribution files.

Do I need repository access to update source control policy files?

Yes, you need repository access to update source control policy files. This skill requires access to modify contribution documentation, AGENTS rules, or policy files to establish and enforce repository rules.

Can I use this to document release strategies and PR flow tightening?

Yes, you can use this to document release strategies and tighten PR flows. It refines source control policies covering structure, branch naming, merge strategies, and commit hygiene applicable during repository bootstrapping or policy updates.

What are the limitations of relying on documentation for merge strategy enforcement?

Relying on documentation for merge strategy enforcement requires manual adherence by contributors. This skill updates contribution guidelines, AGENTS rules, and policy files, but does not directly configure server-side branch protection.