How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/emiliodominguez/flow-skills --skill flow-commitBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
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.
- 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.
- 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.
- Conventional subject:
type(scope): imperative description, following the repository's
types, scopes, length and language. Describe the effect, not a file list.
- 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.
- 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.
- 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.
- 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.
