skills.rest
gracefullight
gracefullightCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

oma-scm

Guide safe Git configuration management with staging and governance checks.

46|2|Updated Mar 23, 2025
Search Tags:#git#worktrees#conventional commits#branching#merge conflicts#codeowners#scm
One-click install
npx skills add https://github.com/gracefullight/krds --skill oma-scm-gracefullight
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: oma-scm
Source: https://github.com/gracefullight/krds/tree/main/.agents/skills/oma-scm
Command: npx skills add https://github.com/gracefullight/krds --skill oma-scm-gracefullight

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

oma-scm helps you perform software configuration management in Git safely, preventing risky staging, conflict mistakes, and audit-unfriendly history changes while ensuring Conventional Commits compliance.

Core Features & Use Cases

  • Safe committing with Conventional Commits: Produces valid <type>(<scope>): <description> commit messages, validates message rules from config, and stages only explicit files.
  • Branching, merging, rebasing, and conflict planning: Guides branching strategy (e.g., GitHub Flow) and provides a structured plan for conflict resolution and history operations.
  • Governance and audit posture: Checks CM governance constraints such as CODEOWNERS requirements, CI expectations for merges, and secret-sensitive path guardrails.
  • Worktree and release/tag orchestration: Supports worktrees and release/tag workflows as part of a controlled CM process.

Quick Start

Use oma-scm to help you commit your current changes safely as a Conventional Commit by staging only the files you specify.

Frequently Asked Questions about oma-scm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I format conventional commits and stage only specific files safely?▼

This Skill validates conventional commit message rules and explicitly stages only the files you specify, preventing accidental commits of unintended changes.

What is the best way to plan for Git merge conflicts and rebasing?▼

The best way to plan for Git merge conflicts is using a structured branching strategy like GitHub Flow, which this Skill guides to provide a clear resolution plan and safe history operations.

How do CODEOWNERS enforcement and CI expectations work for repository governance?▼

CODEOWNERS enforcement and CI-before-merge expectations work by checking governance constraints during Git operations, ensuring required reviews pass and maintaining audit readiness.

Can I manage Git worktrees and release tags in a controlled configuration management process?▼

Yes, you can manage Git worktrees and release tags within a controlled configuration management process, as this Skill orchestrates worktree workflows and release tagging safely.

Does this approach support secret-sensitive path guardrails for safe Git operations?▼

Yes, this approach supports secret-sensitive path guardrails by checking CM governance constraints during staging and Git state inspection to actively avoid committing secrets.

Related Skills

Explore More Software Engineering Skills→
fxckcodefxckcode

git-setup-skill

Automate Git/GitHub repository setup with baseline governance files and CI workflows.

Community
Advanced
u9401066u9401066

git-pusher

Automate Git commit, push, and CI workflow triggering with pre-push validation.

Community
Intermediate
vasilyu1983vasilyu1983
73

git-workflow

Design Git branching strategies, PR workflows, and release automation.

Community
Advanced
zach-sourcezach-source

git

Provide Git commands for staging, committing, branching, merging, and remote operations.

Community
Intermediate