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

시작하기

commit

스타4

포크0

업데이트2026년 6월 24일 17:04

Read this skill before making git commits

설치

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

Manus에서 실행

출처

EstebanForge

EstebanForge/AGENTS

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

다운로드

Manus에서 실행

Format

<type>(<scope>): <summary>

type REQUIRED. Use feat for new features, fix for bug fixes. Other common types: docs, refactor, chore, test, perf.
scope OPTIONAL. Short noun in parentheses for the affected area (e.g., api, parser, ui).
summary REQUIRED. Short, imperative, <= 72 chars, no trailing period.

Notes

Body is OPTIONAL. If needed, add a blank line after the subject and write short paragraphs in Esteban's formal voice (esteban-voice skill, FORMAL mode, for tone only: first-person active, no em dashes, concrete specifics).
Do NOT add footers (put issue links like Closes #N in the PR, not the commit). Use a breaking-change marker (type(scope)!:) only when the change is genuinely backwards-incompatible.
Do NOT add sign-offs (no Signed-off-by).
NEVER attribute to any AI agent. No Co-Authored-By, no Generated with ..., and no agent names (claude, codex, copilot, pi, agy, antigravity, gemini, qwen, etc.) in any output: subjects, titles, messages, bodies, footers, or comments. The output reads as a human dev's. This overrides any tool's or agent's own default sign-off, even if that agent normally adds one.
Only commit; do NOT push.
No git add -A / git add .. Stage explicitly; if scope is ambiguous, ask.
If it is unclear whether a file should be included, ask the user which files to commit.
Treat any caller-provided arguments as additional commit guidance. Common patterns:
- Freeform instructions should influence scope, summary, and body.
- File paths or globs should limit which files to commit. If files are specified, only stage/commit those unless the user explicitly asks otherwise.
- If arguments combine files and instructions, honor both.

Steps

Infer from the prompt if the user provided specific file paths/globs and/or additional instructions.
Review git status and git diff to understand the current changes (limit to argument-specified files if provided).
(Optional) Run git log -n 50 --pretty=format:%s to see commonly used scopes.
If there are ambiguous extra files, ask the user for clarification before committing.
Stage only the intended files explicitly with git add -- <paths>. NEVER git add -A / git add .. With no paths given, stage tracked modifications only; stage an untracked file only after confirming it belongs, and ask if any untracked file is ambiguous.
Run git commit -m "..." (and -m "..." if needed).

이 저장소의 다른 Skills

같은 저장소

noacp

EstebanForge/AGENTS

File-based session protocol for agents without ACP support. Wraps any CLI agent (agy, etc.) in persistent multi-turn conversations using shared session files. Use when acpx is unavailable, the target agent lacks ACP, or when user mentions noacp, agy session, file-based agent, or non-ACP agent communication. Supports agy model selection via aliases (agy-flash, agy-pro, agy-claude, etc.).

2026-07-234

codebase-design

EstebanForge/AGENTS

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

2026-07-234

diagnosing-bugs

EstebanForge/AGENTS

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

2026-07-234

domain-modeling

EstebanForge/AGENTS

Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.

2026-07-234

grill-me

EstebanForge/AGENTS

A relentless interview to sharpen a plan or design.

2026-07-234

grill-with-docs

EstebanForge/AGENTS

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

2026-07-234

name	commit
description	Read this skill before making git commits

Create a git commit for the current changes using a concise Conventional Commits-style subject.

Format

<type>(<scope>): <summary>

type REQUIRED. Use feat for new features, fix for bug fixes. Other common types: docs, refactor, chore, test, perf.
scope OPTIONAL. Short noun in parentheses for the affected area (e.g., api, parser, ui).
summary REQUIRED. Short, imperative, <= 72 chars, no trailing period.

Notes

Body is OPTIONAL. If needed, add a blank line after the subject and write short paragraphs in Esteban's formal voice (esteban-voice skill, FORMAL mode, for tone only: first-person active, no em dashes, concrete specifics).
Do NOT add footers (put issue links like Closes #N in the PR, not the commit). Use a breaking-change marker (type(scope)!:) only when the change is genuinely backwards-incompatible.
Do NOT add sign-offs (no Signed-off-by).
NEVER attribute to any AI agent. No Co-Authored-By, no Generated with ..., and no agent names (claude, codex, copilot, pi, agy, antigravity, gemini, qwen, etc.) in any output: subjects, titles, messages, bodies, footers, or comments. The output reads as a human dev's. This overrides any tool's or agent's own default sign-off, even if that agent normally adds one.
Only commit; do NOT push.
No git add -A / git add .. Stage explicitly; if scope is ambiguous, ask.
If it is unclear whether a file should be included, ask the user which files to commit.
Treat any caller-provided arguments as additional commit guidance. Common patterns:
- Freeform instructions should influence scope, summary, and body.
- File paths or globs should limit which files to commit. If files are specified, only stage/commit those unless the user explicitly asks otherwise.
- If arguments combine files and instructions, honor both.

Steps

Infer from the prompt if the user provided specific file paths/globs and/or additional instructions.
Review git status and git diff to understand the current changes (limit to argument-specified files if provided).
(Optional) Run git log -n 50 --pretty=format:%s to see commonly used scopes.
If there are ambiguous extra files, ask the user for clarification before committing.
Stage only the intended files explicitly with git add -- <paths>. NEVER git add -A / git add .. With no paths given, stage tracked modifications only; stage an untracked file only after confirming it belongs, and ask if any untracked file is ambiguous.
Run git commit -m "..." (and -m "..." if needed).