Skip to content

gracefullight/pkgs / .agents/skills/oma-scm

oma-scm

Verified

Manage Git branches, merges, conflicts, commits, and release baselines. Use for repository history and change-management operations.

resources/codeowners-playbook.md

View on GitHub
# CODEOWNERS Playbook (SCM)

Use this checklist to keep ownership and approval paths healthy.

## What to check

1. `CODEOWNERS` exists in one supported location:
   - `.github/CODEOWNERS`
   - `CODEOWNERS` (repo root)
   - `docs/CODEOWNERS`
2. Critical paths are explicitly owned (avoid relying only on `*` wildcard).
3. Owners in rules are active maintainers (not departed/inactive accounts).
4. Branch protection requires CODEOWNERS review for protected branches.
5. Rules are minimally overlapping and ordered intentionally.

## Baseline template

```text
# Global fallback
* @org/maintainers

# CI and release control
.github/workflows/* @org/devops
cli/commands/migrations/* @org/release-engineering

# Agent system and governance
.agents/hooks/** @org/agent-platform
.agents/workflows/** @org/agent-platform

# Product docs/content
web/content/** @org/docs
docs/** @org/docs
```

## Common anti-patterns

- Only global `*` rule with no critical-path overrides.
- Owners set to individuals only (no team alias).
- Stale owners after team changes.
- Critical infra/security paths missing explicit owners.

## Review cadence

- Re-check CODEOWNERS at least once per quarter.
- Re-check immediately after org/team restructure.
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 implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall