ワンクリックでManusで任意のスキルを実行

git-master

スター17

フォーク0

更新日2026年4月13日 00:47

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/oh-my-team

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