commit

Read this skill before making git commits

Repository: junghan0611/agent-config
Letzte Quellaktivität: 14. Juli 2026 um 03:25
Erkannte Sprache von SKILL.md: Englisch
Sterne: 5
Forks: 0

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.

npx skills add https://github.com/junghan0611/agent-config --skill commit

Der Befehl bleibt in einer Zeile. Scrollen Sie horizontal, um ihn vor dem Kopieren vollständig zu prüfen.

Sie bevorzugen eine lokale Kopie? Laden Sie die Dateien herunter, die SkillsMP derzeit vorliegen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

SKILL.md

Quellanweisungen · Schreibgeschützte Vorschau

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.
Do NOT include breaking-change markers or footers.
Do NOT add sign-offs (no Signed-off-by).
Do NOT add AI attribution (no Generated with Claude, Co-Authored-By: Claude, etc.). Keep the log clean.
Commit only by default. Push only when GLG explicitly requests push or commit + push in the current session. A commit request alone never implies push; commits may be batched before one push so the agenda timeline stays useful.
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 (all changes if no files specified).
Run git commit -m "<subject>" (and -m "<body>" if needed).
If GLG explicitly requested push in the current session:
- verify the current branch, upstream and worktree state;
- use an ordinary push only — never force, bypass hooks or set an unsafe override;
- after push succeeds, stamp the agenda as described below.

Post-push — agenda stamp (required)

The commit is the agent's job; GLG decides whether and when to push. An explicit push request authorizes the agent to execute it. Never infer push from a commit request alone. Once a requested push succeeds, stamp it so the agenda link resolves. Do not stamp local-only commits — the link may break.

# 1. Collect commit info
REMOTE=$(git remote get-url origin)
REPO_URL=$(echo "$REMOTE" | sed -E 's|git@github(-[a-z]+)?\.com:|https://github.com/|;s|\.git$||')
REPO_NAME=$(basename "$REMOTE" .git)
REPO_TAG=$(echo "$REPO_NAME" | tr '[:upper:]' '[:lower:]' | sed 's/[-.]//g')  # lowercase org tag
SHA=$(git rev-parse --short HEAD)
MSG=$(git log -1 --pretty=%s)

# 2. Agenda stamp (with commit link)
SCRIPT="$HOME/.pi/agent/skills/pi-skills/agenda/scripts/agenda-stamp.sh"
[ -x "$SCRIPT" ] || SCRIPT="$HOME/.claude/skills/agenda/scripts/agenda-stamp.sh"  # per-harness fallback
"$SCRIPT" \
  "${REPO_NAME}: ${MSG} [[${REPO_URL}/commit/${SHA}][${SHA}]]" \
  "pi:commit:${REPO_TAG}"

Optional — Google Chat notification (one CLI call, no token cost):

source ~/.env.local && gog chat messages send "$GOG_CHAT_SPACE_ID" \
  --account "$GOG_CHAT_ACCOUNT" \
  --text "🔨 *${REPO_NAME}* commit: ${MSG}
→ ${REPO_URL}/commit/${SHA}"

Notes:

Multiple sequential commits → stamp only the last one.
Env vars (GOG_CHAT_*) live in ~/.env.local (see PRIVATE.md).
If agenda-stamp.sh fails after reasonable retries, STOP and report the exact command + error. Never fall back to Write/Edit/heredoc on the same target.
For release tags (not commits), the stamp uses pi:release: — see the tag-release skill.

Zurück zur Suche Zurück zur Installation

harness-bench

agent-config 루트의 대문자 하네스 벤치(HERMES / OMP / OUROBOROS / HERDR / PRIME / YEGGE) 상태를 보고, 리서치 뒤 그 문서를 갱신한다. 채택이 아니다. 스킬 주입·라이브 setup 금지. 트리거: '하네스 리서치', 'HERMES', 'OMP.md', 'OUROBOROS', 'HERDR', 'PRIME', 'prime-agent', 'YEGGE', '벤치', '대문자 문서', 'harness bench', 'harness research'.

2026-09-09

에이전트가 GLG에게 텔레그램 DM 한 줄을 보낸다. 긴 작업 도중 알릴 것이 생겼을 때, 사람이 터미널 앞에 없어도 닿는 유일한 경로. 양식은 'DM <기기> <리포> <하네스/모델>' + 본문. 트리거: 'dm', 'DM 보내', '텔레그램으로 알려', '나한테 알려줘', '끝나면 알려', 'notify me', 'ping me'.

2026-09-09

entwurf-peek

지금 어느 형제가 어디서 무엇을 하는 중인지 한 장으로 세우고, 다음 한 수(살아있는 형제에게 보낼지 · 잠든 형제를 같은 id로 되세울지 · 새 형제를 열지)를 고를 재료를 주는 판단 도우미. `situation`이 meta-record(사실)와 transcript(추정)를 같은 평면에 올리고, `peek`이 한 세션 안을 들여다본다. 실행은 하지 않는다 — 부르는 것은 entwurf_v2 / entwurf_resume_call / entwurf_fresh_call이고, 무엇을 부를지는 GLG가 정한다. placement(tmux server/window/pane) 사실의 출처가 아니다. 트리거: '누가 뭐 하고 있지', '분신 현황', '지금 살아있는 형제', 'situation', 'entwurf-peek', '누구한테 맡길까', '다시 부를까', 'peek session', '분신 추적'.

2026-09-07

Alle aus diesem Repository ansehen

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.
Do NOT include breaking-change markers or footers.
Do NOT add sign-offs (no Signed-off-by).
Do NOT add AI attribution (no Generated with Claude, Co-Authored-By: Claude, etc.). Keep the log clean.
Commit only by default. Push only when GLG explicitly requests push or commit + push in the current session. A commit request alone never implies push; commits may be batched before one push so the agenda timeline stays useful.
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 (all changes if no files specified).
Run git commit -m "<subject>" (and -m "<body>" if needed).
If GLG explicitly requested push in the current session:
- verify the current branch, upstream and worktree state;
- use an ordinary push only — never force, bypass hooks or set an unsafe override;
- after push succeeds, stamp the agenda as described below.

Post-push — agenda stamp (required)

# 1. Collect commit info
REMOTE=$(git remote get-url origin)
REPO_URL=$(echo "$REMOTE" | sed -E 's|git@github(-[a-z]+)?\.com:|https://github.com/|;s|\.git$||')
REPO_NAME=$(basename "$REMOTE" .git)
REPO_TAG=$(echo "$REPO_NAME" | tr '[:upper:]' '[:lower:]' | sed 's/[-.]//g')  # lowercase org tag
SHA=$(git rev-parse --short HEAD)
MSG=$(git log -1 --pretty=%s)

# 2. Agenda stamp (with commit link)
SCRIPT="$HOME/.pi/agent/skills/pi-skills/agenda/scripts/agenda-stamp.sh"
[ -x "$SCRIPT" ] || SCRIPT="$HOME/.claude/skills/agenda/scripts/agenda-stamp.sh"  # per-harness fallback
"$SCRIPT" \
  "${REPO_NAME}: ${MSG} [[${REPO_URL}/commit/${SHA}][${SHA}]]" \
  "pi:commit:${REPO_TAG}"

Optional — Google Chat notification (one CLI call, no token cost):

source ~/.env.local && gog chat messages send "$GOG_CHAT_SPACE_ID" \
  --account "$GOG_CHAT_ACCOUNT" \
  --text "🔨 *${REPO_NAME}* commit: ${MSG}
→ ${REPO_URL}/commit/${SHA}"

Notes:

Multiple sequential commits → stamp only the last one.
Env vars (GOG_CHAT_*) live in ~/.env.local (see PRIVATE.md).
If agenda-stamp.sh fails after reasonable retries, STOP and report the exact command + error. Never fall back to Write/Edit/heredoc on the same target.
For release tags (not commits), the stamp uses pi:release: — see the tag-release skill.

commit

Quellinformationen

Installationsoptionen

Quelldateien prüfen

Format

Notes

Steps

Post-push — agenda stamp (required)

Mehr aus diesem Repository

Format

Notes

Steps

Post-push — agenda stamp (required)

Mehr aus diesem Repository