oma-scm

1# Software Configuration Management
2 
3## Scheduling
4 
5### Goal
6Perform Git operations with explicit scope, traceable commits, and recoverable history.
7 
8### Intent signature
9- Commit, stage, push, branch, merge, rebase, resolve conflicts, manage worktrees, or inspect SCM governance.
10 
11### When to use
12- Commit and push requests, including Conventional Commit messages and logical splitting.
13- Branch/history operations, releases, baselines, CODEOWNERS, and configuration-management reviews.
14 
15### When NOT to use
16- Implementing a feature or fixing application code -> use the owning specialist.
17- General requirements planning -> use `oma-pm`; security/testing review -> use `oma-qa`.
18 
19### Expected inputs
20Requested Git operation, repository state, and effective `scm` settings from project configuration.
21 
22### Expected outputs
23Requested Git changes or an advisory plan, commit/branch identifiers, checks performed, and unresolved work.
24 
25### Dependencies
26Git CLI; project configuration and hooks. Read the references below only for the selected operation.
27 
28## Structural Flow
29 
30### Entry
31Inspect branch, upstream, staged/unstaged changes, and existing authorization. Select the commit path below or the configuration-management resource for broader operations.
32 
33### Transitions
34- Commit-only request: finish after committing. Push or create a PR only when requested or required by the applicable workflow.
35…