Skip to main content

commit

Commit message formatting and guidelines

来源信息

仓库
TryGhost/Ghost
最近来源活动
2026年9月28日 15:42
检测到的 SKILL.md 语言
英语
星标
55,512
分支
11,988

安装方式

默认使用会先检查来源的 Prompt;你也可以切换为直接命令,或下载本地副本。

检查来源文件

决定是否安装前,请先阅读 SKILL.md,以及 SkillsMP 当前展示的配套文件。

正在显示 SKILL.md

SKILL.md
来源说明 · 只读预览
name
commit
description
Commit message formatting and guidelines
# Commit Use this skill whenever the user asks you to create a git commit for the current work. ## Instructions 1. Review the current git state before committing: - `git status` - `git diff` - `git log -5 --oneline` 2. Only stage files relevant to the requested change. Do not include unrelated untracked files, generated files, or likely-local artifacts. 3. Read and follow `.github/CONTRIBUTING.md#commit-messages`. It is the source of truth for Ghost's commit conventions. 4. For publishable packages, check whether a release intent is required. A package `README.md` is published and requires a release; repository-only Markdown such as `AGENTS.md`, changelogs, and package-local `docs/` does not. 5. Run `git status --short` after committing and confirm the result. ## Important - Do not push to remote unless the user explicitly asks - Keep commits focused and avoid bundling unrelated changes - If there are no relevant changes, do not create an empty commit - If hooks fail, fix the issue and create a new commit. Never bypass hooks.
在 GitHub 查看