返回网格
SKILL / SEED

write-commit

公开中

Create a conventional git commit from staged changes. Use when the user wants to commit, /commit, or write a commit message.

运维 write-commit 1 FILES 4 VIEWS 2026-08-18 07:45
GrokClaude CodeCursorCodex
安装

一键装到本地 agent

和 SkillsMP 一样,先看源码再安装。Grok 用分享链接;Claude / Cursor / Codex 下载 zip 解到技能目录。

META

NAMEwrite-commit
SLUGwrite-commit
SOURCEseed
BYTES609

AI 怎么用

  1. 复制上面的 AI URL
  2. 粘贴到 Claude / ChatGPT / Grok / Cursor
  3. 再说你要做什么,AI 会先读 skill 再动手

SKILL.MD

AGENT READABLE

name: write-commit
description: Create a conventional git commit from staged changes. Use when the user wants to commit, /commit, or write a commit message.

Write Commit

Create one clear conventional commit from the current staged diff.

Steps

  1. Run git status and git diff --staged. If nothing is staged, stop and say so.
  2. Summarize what changed and why, in one sentence.
  3. Write a message: type(scope): summary — types are feat, fix, docs, refactor, test, chore.
  4. Keep the subject under 72 characters. No trailing period.
  5. Commit with that message. Do not push unless asked.
FULL BUNDLE (1 files)
# Agent Skill Package: write-commit

You are loading a published Agent Skill. Follow SKILL.md exactly.
Supporting files from the original zip are inlined below.
When SKILL.md says to read `references/...` or `scripts/...`, use the matching FILE section here — do not say the file is missing.

Canonical URL: https://skill.hk/s/write-commit.md
Human page: https://skill.hk/s/write-commit

Files (1):
- SKILL.md

========================================================================
FILE: SKILL.md
========================================================================

---
name: write-commit
description: Create a conventional git commit from staged changes. Use when the user wants to commit, /commit, or write a commit message.
---

# Write Commit

Create one clear conventional commit from the current staged diff.

## Steps

1. Run `git status` and `git diff --staged`. If nothing is staged, stop and say so.
2. Summarize what changed and why, in one sentence.
3. Write a message: `type(scope): summary` — types are feat, fix, docs, refactor, test, chore.
4. Keep the subject under 72 characters. No trailing period.
5. Commit with that message. Do not push unless asked.
SKILL GRID · 上传 ZIP 或 GitHub 链接,把技能变成一张可分享的卡 ■■□■ GOOGLE 四色 · PIXEL DECK