oma-scm

Installation
SKILL.md

Software configuration management — SCM (oma-scm)

Scheduling

Goal

Manage Git and software configuration management safely: commits, branches, merges, worktrees, releases, baselines, audit posture, CODEOWNERS, and Conventional Commits.

Intent signature

  • User asks to commit, stage, branch, merge, rebase, cherry-pick, tag, release, resolve conflicts, manage worktrees, inspect SCM posture, or apply Conventional Commits.
  • User needs safe Git operations with explicit file staging, secret awareness, and CM governance.

This skill is the single place for configuration management (CM) on a software repo and for Conventional Commits / safe staging.

When to use

  • Commits: “commit this”, /scm, message type/scope, splitting staged changes into multiple commits.
  • CM / Git: branching (gitflow, GitHub Flow, GitLab Flow, trunk-based), protected branches, merge queue, merge conflicts, rebase, cherry-pick, worktrees, submodules/subtrees, tags and releases.
  • Governance: issue/ADR links, breaking-change footers, changelog or release-tool alignment.
  • Audit posture: signed commits, CI before merge, secret-sensitive paths.
Related skills

More from first-fluke/oh-my-agent

Installs
8
GitHub Stars
928
First Seen
Apr 18, 2026