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

시작하기

git-commit

스타7

포크0

업데이트2026년 3월 21일 04:30

Rules for Git commits, pushes, and PR creation

설치

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

Manus에서 실행

출처

nazozokc

nazozokc/dotfiles

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

다운로드

Manus에서 실행

Git Operation Guidelines

When to Use

When committing files
When pushing to remote

Basic Rules

No Japanese in commits: English only
1 commit = 1 logical change: Do not mix multiple different changes
Meaningful granularity: Split large changes
Branch must always be AI-agent: Always commit and push to AI-agent
Code review before committing: See ../code-review/SKILL.md

Branch Strategy

Working branch: Always use AI-agent
PR target: Merge AI-agent → main
Branch creation: If AI-agent doesn't exist, create it first

Commit Message Format

<type>: <summary>

Type List

type	usage
`feat`	New feature
`fix`	Bug fix
`refactor`	Refactoring
`docs`	Documentation change
`chore`	Build/config change
`style`	Formatting/style change

Examples

feat: add neovim telescope config
fix: resolve fish greeting display bug
chore: update flake.lock
refactor: simplify home-manager modules

Notes

Run git status before committing to confirm changes
Auto-generated files should be committed separately
Never use --force variants before creating a PR

이 저장소의 다른 Skills

같은 저장소

merge-main

nazozokc/dotfiles

Use this skill whenever the user wants to merge the main branch into their current branch. Triggers include phrases like "merge main", "mainをマージ", "mainを取り込む", "mainに追従", "sync with main", "mainの変更を取り込みたい", or any request to bring changes from main into a feature/working branch. Always use this skill — do not improvise git commands without it.

2026-03-307

skills-creator

nazozokc/dotfiles

Template and notes when creating or updating SKILL.md files under skills/

2026-03-307

code-review

nazozokc/dotfiles

Perspectives and rules when conducting a code review

2026-03-217

create-pr

nazozokc/dotfiles

Template, notes, and procedure when creating a Pull Request

2026-03-217

github-actions

nazozokc/dotfiles

When creating, editing, or debugging GitHub Actions workflow YAML files

2026-03-217

linux

nazozokc/dotfiles

Constraints when operating files in an Linux environment

2026-03-217

name	git-commit
description	Rules for Git commits, pushes, and PR creation

Git Operation Guidelines

When to Use

When committing files
When pushing to remote

Basic Rules

No Japanese in commits: English only
1 commit = 1 logical change: Do not mix multiple different changes
Meaningful granularity: Split large changes
Branch must always be AI-agent: Always commit and push to AI-agent
Code review before committing: See ../code-review/SKILL.md

Branch Strategy

Working branch: Always use AI-agent
PR target: Merge AI-agent → main
Branch creation: If AI-agent doesn't exist, create it first

Commit Message Format

<type>: <summary>

Type List

type	usage
`feat`	New feature
`fix`	Bug fix
`refactor`	Refactoring
`docs`	Documentation change
`chore`	Build/config change
`style`	Formatting/style change

Examples

feat: add neovim telescope config
fix: resolve fish greeting display bug
chore: update flake.lock
refactor: simplify home-manager modules

Notes

Run git status before committing to confirm changes
Auto-generated files should be committed separately
Never use --force variants before creating a PR