oma-scm

# 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. ### When NOT to use - Implementing product or application code -> use the relevant domain skill - Debugging runtime failures without a Git or CM operation -> use `oma-debug` - Security, performance, or accessibility review -> use `oma-qa` - Planning feature requirements or decomposing work -> use `oma-pm` ### Expected in...