emiliodominguez/flow-skills

flow-commit

Conventional commit messages and atomic commits.

查看源码

使用方法

  1. 复制安装命令,在自己的智能体环境安装前先检查源码包。
  2. 从原始文档核对所需工具、凭据和支持的宿主。
  3. 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/emiliodominguez/flow-skills --skill flow-commit

开始前需了解

  • 安装不包含模型订阅、API 额度或访问文件的权限。
  • 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

Commit

Make one logical change understandable from history. A message draft, permission to commit, and pushing or opening a pull or merge request are separate outcomes.

Process

Decide the mode first. "Write a commit message" or "message for my staged changes" returns text only: no git add, no git commit, and say that nothing was committed.

  1. Inspect branch, status, staged, unstaged and relevant untracked changes. Read the index with

git diff --cached; git diff alone misses staged content. Preserve unrelated staging and working files.

  1. Group changes by intent. Keep tests, generated artifacts and docs with the behavior they

support; don't split an inseparable change to shrink file count.

  1. Conventional subject: type(scope): imperative description, following the repository's

types, scopes, length and language. Describe the effect, not a file list.

  1. Body: the why and the user-visible effect in one plain sentence (for example "Exports over

10k rows now run in the background and email a download link."), plus constraints, significant tradeoffs and breaking-change migration notes. Never invent rationale or claim unrun checks. Follow the repository's Co-Authored-By / generated-credit convention.

  1. Message-only request: return the message and stop. Authorized commit: stage only intended

paths/hunks. Use git add -p when interactive; in a noninteractive host use scoped paths or inspected patches rather than hanging.

  1. Inspect the final index, run the required gate, commit with hooks enabled. A failed plain

commit creates nothing, so a retry must not amend the previous good commit. After an interrupted explicit amend, check HEAD before retrying.

  1. Verify commit contents and remaining worktree. Report SHA and scope; never claim it is

pushed without remote confirmation.

Anti-patterns

  • git add . with unrelated changes in the index or working tree.
  • Mutating Git for "write me a commit message".
  • Bypassing hooks, weakening checks, or amending an unrelated commit after a failure.
  • Shell-interpolating a multi-line message; use a file or structured argument.

Done when

  • The message describes one logical change and its reason.
  • If committing was requested, the commit matches the intended scope, passes required checks,

and unrelated changes are preserved.

Use flow-ship only for delivery actions already in the user's request.

按任务相关推荐

来自同一仓库

更多 Skills

全部 Skills