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

시작하기

git-commit-style

스타10

포크2

업데이트2026년 4월 4일 15:02

Commit message conventions — compact, precise, complete

설치

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

Manus에서 실행

출처

Getty

Getty/langertha

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

다운로드

Manus에서 실행

Commit Message Style

Format

<summary line — imperative, max ~72 chars>

<body — one line per change, no filler>

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Rules

Summary line: imperative mood ("Add", "Fix", "Rename", "Remove"), describe the primary intent
Body: list every discrete change on its own line, no bullets needed, no prose explanations
Completeness: every file-level change must be mentioned — don't silently lump things together
Brevity: state what changed, not why it's important or how it works — the diff shows that
No filler: no "This commit...", no "In this change...", no "Also..."
No @ symbols: never use @ in commit messages (e.g. write [DBIO] not [@DBIO]) — platforms like GitHub interpret @word as user/org mentions
Language: English
Co-Author: always append the Co-Authored-By line when Claude wrote or co-wrote the changes

Examples

Good:

Rename _dbic_connect_attributes to _dbio_connect_attributes

Storage/DBI.pm: accessor declaration and two call sites
Schema/Versioned.pm: one call site

Good:

Migrate to [@DBIO] bundle, fix _Util rename, add POD

Switch dist.ini from [@Author::GETTY] to [@DBIO].
Fix DBIO::_Util -> DBIO::Util in Storage::ASE.
Fix _dbic_cinnect_attributes typo in Storage::FreeTDS.
Add inline POD to all four modules.
Clean up cpanfile, remove deps already in DBIO core.
Add CLAUDE.md and README.md.

Bad (too vague):

Update driver code and documentation

Bad (too verbose):

This commit updates the Sybase driver distribution to use the new
[@DBIO] Dist::Zilla plugin bundle instead of the previous [@Author::GETTY]
bundle. Additionally, it fixes an issue where...

Multi-repo commits

When committing across multiple repos in a workspace, each repo gets its own commit with its own message. Don't reference other repos in the message.

HEREDOC usage

Always pass commit messages via HEREDOC to preserve formatting:

git commit -m "$(cat <<'EOF'
Summary line

Body lines here.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
EOF
)"

이 저장소의 다른 Skills

같은 저장소

karr

Getty/langertha

Use when managing Git-native kanban tasks or shared helper refs with the karr CLI in agent workflows.

2026-06-2610

langertha-adr

Getty/langertha

How Langertha records Architecture Decision Records: the house docs/adr/ format, what counts as ADR-worthy in an LLM-engine framework, and the structure-first method for backfilling decisions already baked into the engine/role/value-object mesh.

2026-06-2610

langertha-github-issues

Getty/langertha

Langertha's PUBLIC issue tracker — real humans' bug reports and feature requests, hosted on GitHub (github.com/Getty/langertha) and reached with the `gh` CLI. Read this whenever GitHub, `gh`, public issues, pull requests, or user bug reports come up. NOT the AI/agent work board (that is karr). HARD RULE: never touch GitHub issues — not even read — unless the user explicitly tells you to.

2026-06-2610

perl-moose

Getty/langertha

Moose-Klassen — Attribute, Roles vs. Inheritance, BUILD/BUILDARGS, Type-Constraints, MooseX::Singleton, make_immutable, Method-Modifier.

2026-05-1510

perl-ai-langertha

Getty/langertha

Langertha LLM framework — Engine creation, Raider autonomous agents, MCP tool integration, plugin system

2026-04-2610

perl-io-async-future

Getty/langertha

Async Perl with IO::Async, Future, Future::AsyncAwait — lifecycle, retention, cancellation, reconnect patterns from PEVANS modules and battle-tested fixes

2026-04-0710

Commit Message Style

Format

<summary line — imperative, max ~72 chars> <body — one line per change, no filler> Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Rules

Summary line: imperative mood ("Add", "Fix", "Rename", "Remove"), describe the primary intent

Body: list every discrete change on its own line, no bullets needed, no prose explanations

Completeness: every file-level change must be mentioned — don't silently lump things together

Brevity: state what changed, not why it's important or how it works — the diff shows that

No filler: no "This commit...", no "In this change...", no "Also..."

No @ symbols: never use @ in commit messages (e.g. write [DBIO] not [@DBIO]) — platforms like GitHub interpret @word as user/org mentions

Language: English

Co-Author: always append the Co-Authored-By line when Claude wrote or co-wrote the changes

Examples

Good:

Rename _dbic_connect_attributes to _dbio_connect_attributes Storage/DBI.pm: accessor declaration and two call sites Schema/Versioned.pm: one call site

Good:

Migrate to [@DBIO] bundle, fix _Util rename, add POD Switch dist.ini from [@Author::GETTY] to [@DBIO]. Fix DBIO::_Util -> DBIO::Util in Storage::ASE. Fix _dbic_cinnect_attributes typo in Storage::FreeTDS. Add inline POD to all four modules. Clean up cpanfile, remove deps already in DBIO core. Add CLAUDE.md and README.md.

Bad (too vague):

Update driver code and documentation

Bad (too verbose):

This commit updates the Sybase driver distribution to use the new [@DBIO] Dist::Zilla plugin bundle instead of the previous [@Author::GETTY] bundle. Additionally, it fixes an issue where...

Multi-repo commits

When committing across multiple repos in a workspace, each repo gets its own commit with its own message. Don't reference other repos in the message.

HEREDOC usage

Always pass commit messages via HEREDOC to preserve formatting:

git commit -m "$(cat <<'EOF' Summary line Body lines here. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> EOF )"

name	git-commit-style
description	Commit message conventions — compact, precise, complete
user-invocable	false