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

git-commit

스타15

포크3

업데이트2026년 1월 28일 09:25

Generate intelligent, conventional commit messages based on staged changes. Analyzes diffs, categorizes changes, and creates meaningful commit messages. Use when ready to commit changes and want high-quality commit history.

설치

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

Manus에서 실행

출처

richardcb

richardcb/oh-my-gemini

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

다운로드

Manus에서 실행

Git Commit Skill

Goal

Generate meaningful, conventional commit messages by analyzing staged changes. Creates commits that tell a story and make git history useful.

Activation Triggers

User says "commit", "git commit", or "save changes"
User asks for a commit message
After completing implementation tasks

Process

1. Check Git Status

# Check if in a git repo
git rev-parse --git-dir 2>/dev/null || echo "NOT_A_GIT_REPO"

# Check staged changes
git diff --cached --stat

# Check unstaged changes
git status --short

2. Analyze Staged Changes

# Get detailed diff of staged changes
git diff --cached

# Get list of files changed
git diff --cached --name-only

# Get change statistics
git diff --cached --shortstat

3. Categorize Changes

Determine the commit type based on changes:

Type	Description	Examples
`feat`	New feature	New endpoint, new component, new capability
`fix`	Bug fix	Error handling, logic correction
`docs`	Documentation	README, comments, JSDoc
`style`	Formatting	Whitespace, semicolons, no logic change
`refactor`	Code restructuring	Rename, extract function, no behavior change
`perf`	Performance	Optimization, caching
`test`	Tests	New tests, test fixes
`chore`	Maintenance	Dependencies, build config
`ci`	CI/CD	GitHub Actions, deployment

4. Identify Scope

Look at changed files to determine scope:

Single component: Use component name as scope
Multiple related files: Use feature/module name
Many unrelated files: Consider splitting commit

5. Generate Commit Message

Format

<type>(<scope>): <subject>

<body>

<footer>

Subject Rules

Max 50 characters
Imperative mood ("add" not "added")
No period at end
Lowercase

Body Rules

Wrap at 72 characters
Explain what and why, not how
Separate from subject with blank line

Footer Rules

Reference issues: Closes #123
Breaking changes: BREAKING CHANGE: description

6. Execute Commit

# Commit with generated message
git commit -m "<type>(<scope>): <subject>" -m "<body>"

# Or if user wants to edit
git commit -e -m "<generated message>"

Examples

Simple Feature

# Staged: src/components/Button.tsx (new file)
git commit -m "feat(button): add reusable Button component"

Bug Fix with Context

# Staged: src/api/auth.ts (modified)
git commit -m "fix(auth): handle expired refresh tokens

Previously, expired refresh tokens caused a 500 error.
Now properly returns 401 and clears the session.

Closes #456"

Multiple Files, Same Feature

# Staged: src/api/users.ts, src/types/user.ts, tests/users.test.ts
git commit -m "feat(users): add user profile endpoint

- Add GET /api/users/:id endpoint
- Add User type definitions
- Add integration tests

Closes #789"

Breaking Change

git commit -m "refactor(api)!: change response format to JSON:API

BREAKING CHANGE: All API responses now follow JSON:API spec.
Clients must update to handle the new response structure.

Migration guide: docs/migration-v2.md"

Interactive Mode

If changes are complex, ask user:

I see changes to multiple areas:
- 3 files in src/components/ (UI changes)
- 2 files in src/api/ (backend changes)
- 1 file in tests/ (test updates)

Would you like to:
1. Create a single commit for all changes
2. Split into multiple focused commits
3. Let me suggest a commit message and you review

[1/2/3]?

Verification

After committing:

# Show the commit
git log -1 --pretty=format:"%h %s%n%n%b"

# Verify it's pushed (if applicable)
git status

Best Practices Enforced

Atomic commits: One logical change per commit
Meaningful messages: Explain why, not just what
Conventional format: Enables automated changelogs
Issue linking: Connect commits to tickets
No WIP commits: Clean, squashable history

Output Format

📝 Commit Message Generated

Type: feat
Scope: authentication
Subject: add OAuth2 login flow

Body:
Implement OAuth2 authorization code flow with PKCE.
Supports Google and GitHub providers.

Footer:
Closes #123

---

Execute commit? [Y/n/edit]

이 저장소의 다른 Skills

같은 저장소

code-review

richardcb/oh-my-gemini

Perform thorough code review and audit of implemented features. Compares implementation against the technical plan, checks for AI-specific risks, and provides actionable feedback. Activate for: review, audit, code quality assessment, security review.

2026-03-0115

conductor-setup

richardcb/oh-my-gemini

Initialize Conductor workflow in a project. Bundles all necessary templates for product context, tech stack, workflow, and tracks. v1.0: Hooks handle phase enforcement - setup focuses on file creation.

2026-03-0115

ralph-mode

richardcb/oh-my-gemini

Persistence mode instructions for autonomous task completion. Activated when the user includes "ralph", "persistent", or "don't give up" in their prompt. Provides structured guidance for working through tasks systematically.

2026-03-0115

research-methodology

richardcb/oh-my-gemini

Structured research methodology for finding documentation, investigating APIs, and synthesizing technical information. Guides systematic research with source verification and organized output. Activate for: research, documentation lookup, investigate, explore concepts.

2026-03-0115

technical-planning

richardcb/oh-my-gemini

Plan and design a detailed, phased technical implementation from a PRD. Creates actionable task lists with guardrails for resource efficiency, error handling, and type safety. Activate for: plan, design, technical planning, task breakdown.

2026-03-0115

documentation

richardcb/oh-my-gemini

Generate documentation for implemented features. The actual code is always the source of truth - document what was built, not what was planned. Creates code comments, README updates, and developer guides as appropriate.

2026-02-2615

name	git-commit
description	Generate intelligent, conventional commit messages based on staged changes. Analyzes diffs, categorizes changes, and creates meaningful commit messages. Use when ready to commit changes and want high-quality commit history.

Git Commit Skill

Goal

Generate meaningful, conventional commit messages by analyzing staged changes. Creates commits that tell a story and make git history useful.

Activation Triggers

User says "commit", "git commit", or "save changes"
User asks for a commit message
After completing implementation tasks

Process

1. Check Git Status

# Check if in a git repo
git rev-parse --git-dir 2>/dev/null || echo "NOT_A_GIT_REPO"

# Check staged changes
git diff --cached --stat

# Check unstaged changes
git status --short

2. Analyze Staged Changes

# Get detailed diff of staged changes
git diff --cached

# Get list of files changed
git diff --cached --name-only

# Get change statistics
git diff --cached --shortstat

3. Categorize Changes

Determine the commit type based on changes:

Type	Description	Examples
`feat`	New feature	New endpoint, new component, new capability
`fix`	Bug fix	Error handling, logic correction
`docs`	Documentation	README, comments, JSDoc
`style`	Formatting	Whitespace, semicolons, no logic change
`refactor`	Code restructuring	Rename, extract function, no behavior change
`perf`	Performance	Optimization, caching
`test`	Tests	New tests, test fixes
`chore`	Maintenance	Dependencies, build config
`ci`	CI/CD	GitHub Actions, deployment

4. Identify Scope

Look at changed files to determine scope:

Single component: Use component name as scope
Multiple related files: Use feature/module name
Many unrelated files: Consider splitting commit

5. Generate Commit Message

Format

<type>(<scope>): <subject>

<body>

<footer>

Subject Rules

Max 50 characters
Imperative mood ("add" not "added")
No period at end
Lowercase

Body Rules

Wrap at 72 characters
Explain what and why, not how
Separate from subject with blank line

Footer Rules

Reference issues: Closes #123
Breaking changes: BREAKING CHANGE: description

6. Execute Commit

# Commit with generated message
git commit -m "<type>(<scope>): <subject>" -m "<body>"

# Or if user wants to edit
git commit -e -m "<generated message>"

Examples

Simple Feature

# Staged: src/components/Button.tsx (new file)
git commit -m "feat(button): add reusable Button component"

Bug Fix with Context

# Staged: src/api/auth.ts (modified)
git commit -m "fix(auth): handle expired refresh tokens

Previously, expired refresh tokens caused a 500 error.
Now properly returns 401 and clears the session.

Closes #456"

Multiple Files, Same Feature

# Staged: src/api/users.ts, src/types/user.ts, tests/users.test.ts
git commit -m "feat(users): add user profile endpoint

- Add GET /api/users/:id endpoint
- Add User type definitions
- Add integration tests

Closes #789"

Breaking Change

git commit -m "refactor(api)!: change response format to JSON:API

BREAKING CHANGE: All API responses now follow JSON:API spec.
Clients must update to handle the new response structure.

Migration guide: docs/migration-v2.md"

Interactive Mode

If changes are complex, ask user:

I see changes to multiple areas:
- 3 files in src/components/ (UI changes)
- 2 files in src/api/ (backend changes)
- 1 file in tests/ (test updates)

Would you like to:
1. Create a single commit for all changes
2. Split into multiple focused commits
3. Let me suggest a commit message and you review

[1/2/3]?

Verification

After committing:

# Show the commit
git log -1 --pretty=format:"%h %s%n%n%b"

# Verify it's pushed (if applicable)
git status

Best Practices Enforced

Atomic commits: One logical change per commit
Meaningful messages: Explain why, not just what
Conventional format: Enables automated changelogs
Issue linking: Connect commits to tickets
No WIP commits: Clean, squashable history

Output Format

📝 Commit Message Generated

Type: feat
Scope: authentication
Subject: add OAuth2 login flow

Body:
Implement OAuth2 authorization code flow with PKCE.
Supports Google and GitHub providers.

Footer:
Closes #123

---

Execute commit? [Y/n/edit]