Run any Skill in Manus with one click

git-master

Stars17

Forks0

UpdatedApril 13, 2026 at 00:47

Utility: Atomic commit workflow. Analyzes changes, groups into logical commits, writes clear commit messages. Solo operation, no team needed.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

erkandogan

erkandogan/oh-my-team

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	git-master
description	Utility: Atomic commit workflow. Analyzes changes, groups into logical commits, writes clear commit messages. Solo operation, no team needed.
disable-model-invocation	true
argument-hint	[optional: commit message override]

Git Master - Atomic Commit Workflow

Create clean, atomic commits from the current changes.

Protocol

Step 1: Analyze Changes

git status
git diff --stat
git diff

Understand what changed and why.

Step 2: Group Into Logical Commits

If changes span multiple concerns, group them:

Each commit should be one logical change
Each commit should leave the codebase in a buildable state
Order commits so dependencies come first

Step 3: Write Commit Messages

Format:

<type>(<scope>): <description>

<body - what and why, not how>

Types: feat, fix, refactor, test, docs, chore, perf, style

Rules:

Subject line: imperative mood, lowercase, no period, under 72 chars
Body: explain WHY, not WHAT (the diff shows what)
Reference issues if applicable

Step 4: Stage and Commit

For each logical group:

Stage specific files: git add <files>
Commit with the prepared message
Verify: git log --oneline -1

Step 5: Verify

Run git log --oneline -5 to show recent commits
Confirm each commit is atomic and self-contained

Anti-Patterns

NEVER git add . blindly
NEVER commit .env, credentials, or secrets
NEVER create empty commits
NEVER amend published commits without asking
NEVER force push without explicit permission

More from this repository

same repository

ai-slop-remover

erkandogan/oh-my-team

Utility: Detect and remove AI-generated code slop. Finds unnecessary comments, over-engineering, verbose error handling, premature abstractions. Solo operation, no team needed.

2026-04-1317

deep-debug

erkandogan/oh-my-team

Multi-hypothesis parallel debugging with agent teams. Spawns multiple investigators to test competing theories simultaneously. They challenge each other's findings.

2026-04-1317

plan

erkandogan/oh-my-team

Strategic planning workflow. Creates an agent team with Prometheus (interview), Metis (gap analysis), and optionally Momus (plan review). Generates detailed work plans to .sisyphus/plans/.

2026-04-1317

review-work

erkandogan/oh-my-team

5-agent parallel review gate using agent teams. Spawns Goal Verification, QA Execution, Code Quality, Security Audit, and Context Mining teammates. ALL must pass.

2026-04-1317

start-work

erkandogan/oh-my-team

Execute a work plan using Atlas orchestration with agent teams. Reads plan from .sisyphus/plans/, creates a team, spawns specialized teammates to execute tasks in parallel waves.

2026-04-1317

frontend-ui-ux

erkandogan/oh-my-team

Frontend and UI/UX development guidance. Provides patterns for responsive design, accessibility, component architecture, state management, and visual consistency. Load this skill when working on any frontend task.

2026-04-1017

name	git-master
description	Utility: Atomic commit workflow. Analyzes changes, groups into logical commits, writes clear commit messages. Solo operation, no team needed.
disable-model-invocation	true
argument-hint	[optional: commit message override]

Git Master - Atomic Commit Workflow

Create clean, atomic commits from the current changes.

Protocol

Step 1: Analyze Changes

git status
git diff --stat
git diff

Understand what changed and why.

Step 2: Group Into Logical Commits

If changes span multiple concerns, group them:

Each commit should be one logical change
Each commit should leave the codebase in a buildable state
Order commits so dependencies come first

Step 3: Write Commit Messages

Format:

<type>(<scope>): <description>

<body - what and why, not how>

Types: feat, fix, refactor, test, docs, chore, perf, style

Rules:

Subject line: imperative mood, lowercase, no period, under 72 chars
Body: explain WHY, not WHAT (the diff shows what)
Reference issues if applicable

Step 4: Stage and Commit

For each logical group:

Stage specific files: git add <files>
Commit with the prepared message
Verify: git log --oneline -1

Step 5: Verify

Run git log --oneline -5 to show recent commits
Confirm each commit is atomic and self-contained

Anti-Patterns

NEVER git add . blindly
NEVER commit .env, credentials, or secrets
NEVER create empty commits
NEVER amend published commits without asking
NEVER force push without explicit permission