New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Mcaf Source Control

by managedcode in managedcode/Storage

Set or refine source-control policy for repository structure, branch naming, merge strategy, commit hygiene, and secrets-in-git discipline.

MITAuto-check passedAgent Workflows

Install Mcaf Source Control

skills CLI
$ npx skills add managedcode/Storage --skill mcaf-source-control -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install managedcode/Storage mcaf-source-control --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/managedcode/Storage.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/mcaf-source-control .claude/skills/mcaf-source-control && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
mcaf-source-control
GitHub stars
138
Token cost
~902 tokens
SKILL.md length
430 words
Files
3 (incl. references)
Skills in repo
41
Repo updated
First seen
Licence
MIT

At a glance

Set or refine source-control policy for repository structure, branch naming, merge strategy, commit hygiene, and secrets-in-git discipline.

  • Works in 3 steps: Read the nearest AGENTS.md and confirm… → Run this skill's Workflow through the… → Return the Required Result Format with…
  • Bootstrapping a repo
  • SKILL.md covers Trigger On, Value, Do Not Use For and Inputs, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Mcaf Source Control is an agent skill from managedcode/Storage. Set or refine source-control policy for repository structure, branch naming, merge strategy, commit hygiene, and secrets-in-git discipline. Use when bootstrapping a repo, tightening PR flow, or documenting branch and release policy.

Its SKILL.md is about 900 tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/naming-branches.md` and `references/source-control.md`). Compatibility notes: Requires repository access; may update contribution docs, AGENTS rules, or repository policy files.

It sits in Agent Workflows, covering Git workflow. It works with Git. The repository describes itself as: Storage library provides a universal interface for accessing and manipulating data in different cloud blob storage providers. The licence is MIT.

When your agent uses it

  • Bootstrapping a repo
  • Tightening PR flow
  • Documenting branch and release policy

Example prompts

  • “/mcaf-source-control”

Requirements

  • Compatibility (from SKILL.md): Requires repository access; may update contribution docs, AGENTS rules, or repository policy files.

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Read the nearest AGENTS.md and confirm scope and constraints.
  2. Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
  3. Return the Required Result Format with concrete artifacts and verification evidence.

What it can do on your machine

Read from SKILL.md and the folder at commit 5d32121. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires repository access; may update contribution docs, AGENTS rules, or repository policy files.

    From compatibility in the SKILL.md frontmatter.

Context cost

Mcaf Source Control loads about 902 tokens when it runs, and up to ~1.2k if it reads all its reference files. Until then it costs about 63 tokens; SKILL.md has 430 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~63
When it runs · the whole SKILL.md, loaded when a task matches
~902
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from managedcode/Storage at commit 5d32121, republished under its MIT licence (© managedcode). 430 words, ~902 tokens.

Download SKILL.mdSave it as .claude/skills/mcaf-source-control/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
mcaf-source-control
description
Set or refine source-control policy for repository structure, branch naming, merge strategy, commit hygiene, and secrets-in-git discipline. Use when bootstrapping a repo, tightening PR flow, or documenting branch and release policy.
compatibility
Requires repository access; may update contribution docs, AGENTS rules, or repository policy files.

MCAF: Source Control

Trigger On

  • bootstrapping source-control policy
  • tightening branch, merge, or PR rules
  • documenting commit or release hygiene
  • dealing with secrets-in-git or repository structure issues

Value

  • produce a concrete project delta: code, docs, config, tests, CI, or review artifact
  • reduce ambiguity through explicit planning, verification, and final validation skills
  • leave reusable project context so future tasks are faster and safer

Do Not Use For

  • CI/CD workflow design with no source-control policy change
  • one-off git commands that do not alter repo policy

Inputs

  • current branching and merge flow
  • release strategy and versioning expectations
  • secret-handling and repository-structure constraints

Quick Start

  1. Read the nearest AGENTS.md and confirm scope and constraints.
  2. Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
  3. Return the Required Result Format with concrete artifacts and verification evidence.

Workflow

  1. Agree on merge and release strategy before scaling implementation.
  2. Keep branch and PR rules explicit in-repo.
  3. Treat secrets in git history as a critical incident, not cleanup noise.
  4. Use concrete policy language, not hand-waving.

Deliver

  • clear branch and merge strategy
  • updated contribution or governance docs
  • safer repository hygiene around commits, PRs, and secrets

Validate

  • naming and merge rules are explicit
  • release/versioning implications are documented where needed
  • secret hygiene is treated as policy, not tribal knowledge
Show full SKILL.md (216 more words)Show less

Ralph Loop

Use the Ralph Loop for every task, including docs, architecture, testing, and tooling work.

  1. Plan first (mandatory):
    • analyze current state
    • define target outcome, constraints, and risks
    • write a detailed execution plan
    • list final validation skills to run at the end, with order and reason
  2. Execute one planned step and produce a concrete delta.
  3. Review the result and capture findings with actionable next fixes.
  4. Apply fixes in small batches and rerun the relevant checks or review steps.
  5. Update the plan after each iteration.
  6. Repeat until outcomes are acceptable or only explicit exceptions remain.
  7. If a dependency is missing, bootstrap it or return status: not_applicable with explicit reason and fallback path.
Required Result Format
  • status: complete | clean | improved | configured | not_applicable | blocked
  • plan: concise plan and current iteration step
  • actions_taken: concrete changes made
  • validation_skills: final skills run, or skipped with reasons
  • verification: commands, checks, or review evidence summary
  • remaining: top unresolved items or none

For setup-only requests with no execution, return status: configured and exact next commands.

Load References

  • read references/source-control.md first
  • open references/naming-branches.md only when the task is specifically about branch naming

Example Requests

  • "Define branch naming and merge rules for this repo."
  • "Document how releases and component versions should work."
  • "Tighten our source-control policy after a secrets leak."

© managedcode, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in .codex/skills/mcaf-source-control of managedcode/Storage.

  • SKILL.md
  • references/naming-branches.md
  • references/source-control.md

Open the folder on GitHubat commit 5d32121

Compare with similar skills

Mcaf Source Control next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Mcaf Source Control compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Mcaf Source Control this skillmanagedcode/Storage138—~902Automated safety check: PassMIT
Foremergenaw103/foremerge536—~2.4kAutomated safety check: PassApache-2.0
Huashu Agent Swarmalchaincyf/huashu-skills1.7k—~576Automated safety check: PassMIT
Session Catchup and Handoffposhan0126/dotclaude871—~811Automated safety check: PassMIT
PrepAIOSAI/AIPass288—~880Automated safety check: PassMIT
Memorix Git MemoryAVIDS2/memorix835—~318Automated safety check: PassApache-2.0

Similar skills

  • Foremerge

    naw103/foremerge

    Coordinate parallel coding agents with Foremerge's local Git-compatible CLI and MCP server.

    536 GitHub stars~2.4k tokensUpdated 3 days ago
    Agent WorkflowsAuto-check passed

  • Huashu Agent Swarm

    alchaincyf/huashu-skills

    多Agent蜂群并行协作，纯git自组织，适合大型项目开发。当用户提到"蜂群模式"、"多agent"、"并行开发"、"agent swarm"时使用。

    1.7k GitHub stars~576 tokensUpdated 15 days ago
    Agent WorkflowsAuto-check passed

  • Session Catchup and Handoff

    poshan0126/dotclaude

    Rebuilds working context after /clear by reading a handoff note and the branch's git state, or writes that handoff note before a session ends.

    871 GitHub stars~811 tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed

  • Prep

    AIOSAI/AIPass

    Session wrap-up. An agent skill from AIOSAI/AIPass.

    288 GitHub stars~880 tokensUpdated 2 days ago
    Agent WorkflowsAuto-check passed

  • Memorix Git Memory

    AVIDS2/memorix

    A skill your agent uses when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.

    835 GitHub stars~318 tokensUpdated 5 days ago
    Agent WorkflowsAuto-check passed

  • Darwin Skill

    HHU3637kr/skills

    Darwin Skill (达尔文.skill): autonomous skill optimizer inspired by Karpathy's autoresearch.

    145 GitHub starsUsed in 1 repo~2.2k tokens
    Agent WorkflowsAuto-check passed

More from managedcode/Storage

All 41 skills in this repo

  • Mcaf Adr Writing

    managedcode/Storage

    Create or update an ADR under docs/ADR/ for architectural decisions, dependency changes, data-model changes, or cross-cutting policy shifts.

    138 GitHub stars~951 tokensUpdated today
    Auto-check passed

  • Mcaf Agile Delivery

    managedcode/Storage

    Shape delivery workflow around backlog quality, roles, ceremonies, and engineering feedback.

    138 GitHub stars~883 tokensUpdated today
    Auto-check passed

  • Mcaf Architecture Overview

    managedcode/Storage

    Create or update docs/Architecture.md as the global architecture map for a solution.

    138 GitHub stars~950 tokensUpdated today
    Auto-check passed

  • Mcaf CI CD

    managedcode/Storage

    Design or refine CI/CD workflows, quality gates, release flow, and safe AI-assisted pipeline authoring.

    138 GitHub stars~981 tokensUpdated today
    Auto-check passed

  • Mcaf Code Review

    managedcode/Storage

    Prepare for, perform, or tighten code review workflow: PR scope, review checklist, reviewer expectations, and merge hygiene.

    138 GitHub stars~957 tokensUpdated today
    Auto-check passed

  • Mcaf Devex

    managedcode/Storage

    Improve developer experience for multi-component solutions: onboarding, F5 contract, cross-platform tasks, local inner loop, and reproducible setup.

    138 GitHub stars~911 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Mcaf Source Control

What does Mcaf Source Control do?

Set or refine source-control policy for repository structure, branch naming, merge strategy, commit hygiene, and secrets-in-git discipline. Mcaf Source Control is an agent skill from managedcode/Storage. Set or refine source-control policy for repository structure, branch naming, merge strategy, commit hygiene, and secrets-in-git discipline.

When should I use Mcaf Source Control?

Mcaf Source Control fits situations like: bootstrapping a repo; tightening PR flow; documenting branch and release policy.

How do I install Mcaf Source Control in Claude Code?

Run `npx skills add managedcode/Storage --skill mcaf-source-control -a claude-code`. Or copy the skill folder (.codex/skills/mcaf-source-control in managedcode/Storage) into .claude/skills/mcaf-source-control in your project. Claude Code loads it when a task matches its description.

How do I install Mcaf Source Control in Codex?

Run `npx skills add managedcode/Storage --skill mcaf-source-control -a codex`. Or copy the skill folder (.codex/skills/mcaf-source-control in managedcode/Storage) into .agents/skills/mcaf-source-control in your project. Codex loads it when a task matches its description.

Can I use Mcaf Source Control in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add managedcode/Storage --skill mcaf-source-control -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mcaf-source-control, .gemini/skills/mcaf-source-control, .github/skills/mcaf-source-control and .opencode/skills/mcaf-source-control in your project.

What does Mcaf Source Control need to run?

SKILL.md names no scripts, command-line tools or credentials: Mcaf Source Control is instructions for the agent only. Compatibility (from SKILL.md): Requires repository access; may update contribution docs, AGENTS rules, or repository policy files..

Does Mcaf Source Control access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Mcaf Source Control safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Mcaf Source Control use?

Mcaf Source Control is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Mcaf Source Control use?

About 902 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 337 tokens, read only when the agent opens those files.

What are the alternatives to Mcaf Source Control?

Skills that share tags, products or a category with Mcaf Source Control: Foremerge (naw103/foremerge, 536 stars), Huashu Agent Swarm (alchaincyf/huashu-skills, 1.7k stars), Session Catchup and Handoff (poshan0126/dotclaude, 871 stars) and Prep (AIOSAI/AIPass, 288 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Mcaf Source Control?

managedcode (a GitHub organization) maintains it in managedcode/Storage, which has 138 GitHub stars. The repository holds 41 skills in this directory. The repository was last updated on October 7, 2026.

Source: managedcode/Storage on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.