gracefullight/pkgs / .agents/skills/oma-scm
oma-scm
VerifiedManage Git branches, merges, conflicts, commits, and release baselines. Use for repository history and change-management operations.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.9 KB |
| resources/cm-operations.md | markdown | 2.9 KB |
| resources/codeowners-playbook.md | markdown | 1.2 KB |
| resources/conventional-commits.md | markdown | 3.2 KB |
| resources/merge-risk.md | markdown | 3.5 KB |
| resources/onboarding-risk-signals.md | markdown | 2.0 KB |
resources/onboarding-risk-signals.md
View on GitHub# Onboarding Risk Signals (SCM)
Use these lightweight SCM metrics to quickly estimate maintenance risk in an unfamiliar repository.
## 1) High-Churn Files
Frequent edits often indicate maintenance hotspots or unstable boundaries.
```bash
git log --format=format: --name-only --since="1 year ago" | sort | uniq -c | sort -nr | head -20
```
## 2) Ownership / Bus Factor
Detect concentration risk and potential knowledge silos.
```bash
git shortlog -sn --no-merges
```
Heuristic:
- One author > 60% of commits can indicate bus-factor risk.
- If top contributors are inactive for 6+ months, flag continuity risk.
- With squash-merge-heavy teams, treat commit-count ownership as approximate.
## 3) Bug Hotspots
Approximate bug-prone files from bug-fix commit history.
```bash
git log -i -E --grep="fix|bug|broken" --name-only --format='' | sort | uniq -c | sort -nr | head -20
```
Cross-reference with high-churn list to identify high-risk files.
## 4) Development Velocity Trend
Inspect monthly activity and momentum shifts.
```bash
git log --format='%ad' --date=format:'%Y-%m' | sort | uniq -c
```
Heuristic:
- Stable/increasing trend suggests healthy delivery cadence.
- 50%+ sudden drop can indicate staffing or ownership disruption.
- 6-12 month steady decline can indicate project stagnation.
## 5) Revert / Hotfix / Firefighting Signal
Estimate operational reliability from emergency recovery patterns.
```bash
git log --oneline --since="1 year ago" | rg -i "revert|hotfix|emergency|rollback"
```
Heuristic:
- A few incidents per year can be normal.
- Incidents every ~2 weeks suggest unstable release/testing process.
- Zero incidents may mean stable delivery or poor commit labeling.
## Practical Output Template
Report these sections:
- Top churn files (top 10-20)
- Ownership concentration and inactive key contributors
- Bug hotspot overlaps with churn files
- Velocity trend summary (recent 6-12 months)
- Firefighting frequency and confidence level
Always include caveats: squash merges, inconsistent commit labels, and monorepo skew.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |