원클릭으로 Manus에서 모든 스킬 실행

git-master

스타0

포크0

업데이트2026년 7월 11일 18:45

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

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

erkandogan

erkandogan/sodium

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

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

이 저장소의 다른 Skills

같은 저장소

ai-slop-remover

erkandogan/sodium

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

2026-07-110

deep-debug

erkandogan/sodium

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

2026-07-110

plan

erkandogan/sodium

Strategic planning workflow. Creates an agent team with Prometheus (interview), Metis (gap analysis), and optionally Momus (plan review). Plans live as scope chunks in the sodium team brain — recallable across sessions, never as filesystem markdown.

2026-07-110

start-work

erkandogan/sodium

Execute a work plan using Atlas orchestration with agent teams. Reads the plan from the sodium team brain (scope chunk), creates an exec team, spawns specialised teammates to run tasks in parallel waves. Plans live in memory, not in .sisyphus/plans/.

2026-07-110

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	false
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