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

시작하기

commit-multiple

스타0

포크0

업데이트2026년 5월 25일 19:05

Create multiple git commits, one per concern, from changes in the working tree

설치

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

Manus에서 실행

출처

ilyasturki

ilyasturki/claude-skills

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

다운로드

Manus에서 실행

Context

Current git status: !git status
Changes to commit: !if git diff --staged --quiet; then git diff; else git diff --staged; fi
Current branch: !git branch --show-current
Recent commits: !git log --oneline -10 2>/dev/null || echo "No commits yet"

User Context

$ARGUMENTS

Commit Name Rules

Single-line Conventional Commit:

Format: ():
Types: feat, fix, refactor, perf, docs, style, test, build, ci, chore, revert
Description must mention the SPECIFIC thing changed (component name, function, feature, etc.)
Include "!" after type for breaking changes
≤72 chars, lowercase, imperative mood, no period

Your task

Group all working-tree changes (staged and unstaged) by logical concern — application, feature, or purpose. Each group becomes one commit.

Steps:

Review the full diff to identify distinct concerns
git reset HEAD to unstage (only if anything is staged)
For each group, sequentially: a. git add the files (or hunks) for that group b. git commit -m "message" — single-line, no heredocs or $()
Run git status to confirm the tree is clean

If a single file contains hunks for truly distinct concerns (e.g. different commit types or scopes), split them across commits; otherwise keep the whole file in its most relevant commit.

이 저장소의 다른 Skills

같은 저장소

vet

ilyasturki/claude-skills

After a code change, test it end-to-end (bash, browser, or computer use — whichever fits) and then run `/simplify` to review and clean up the changed code. Use to confirm a change works and is tidy before wrapping up.

2026-06-010

commit-push

ilyasturki/claude-skills

Create a git commit and push it

2026-05-290

commit

ilyasturki/claude-skills

Create a git commit

2026-05-290

clarify

ilyasturki/claude-skills

Ask the user for maximum clarifications before acting on a prompt. Use when the user wants to ensure all ambiguity is resolved before work begins.

2026-05-260

readme

ilyasturki/claude-skills

Write or refresh a README that earns the reader's attention — short, honest, with a real visual. Tailored to the project type.

2026-05-260

spec

ilyasturki/claude-skills

Greenfield product spec for an empty repo. Clarifies scope, then challenges the idea — checking whether it already exists and whether the pain is real — before writing a concise spec.md.

2026-05-260

name	commit-multiple
description	Create multiple git commits, one per concern, from changes in the working tree
allowed-tools	Bash(git add:), Bash(git status:), Bash(git commit:), Bash(git reset HEAD:), Bash(git diff:*), Bash(if git diff --staged --quiet; then git diff; else git diff --staged; fi)

Context

Current git status: !git status
Changes to commit: !if git diff --staged --quiet; then git diff; else git diff --staged; fi
Current branch: !git branch --show-current
Recent commits: !git log --oneline -10 2>/dev/null || echo "No commits yet"

User Context

$ARGUMENTS

Commit Name Rules

Single-line Conventional Commit:

Format: ():
Types: feat, fix, refactor, perf, docs, style, test, build, ci, chore, revert
Description must mention the SPECIFIC thing changed (component name, function, feature, etc.)
Include "!" after type for breaking changes
≤72 chars, lowercase, imperative mood, no period

Your task

Group all working-tree changes (staged and unstaged) by logical concern — application, feature, or purpose. Each group becomes one commit.

Steps:

Review the full diff to identify distinct concerns
git reset HEAD to unstage (only if anything is staged)
For each group, sequentially: a. git add the files (or hunks) for that group b. git commit -m "message" — single-line, no heredocs or $()
Run git status to confirm the tree is clean

If a single file contains hunks for truly distinct concerns (e.g. different commit types or scopes), split them across commits; otherwise keep the whole file in its most relevant commit.