Skip to content
pionus

How it works

From your history and staged diff to one message.

The pipeline

  1. Read gitThe log, the branch and git diff --staged.
  2. Infer the styleConvention, scopes and ticket format, from your commit subjects. Messages are in English.
  3. Compact the diffFiles are fitted into a token budget.
  4. Build the promptA system message and a user message.
  5. Ask the modelOn the chosen device, with greedy decoding.
  6. SanitizeThe reply is cleaned up; bad replies are rejected.

Failures and fallbacks

A bad reply gets one retry, then a message built from the file list. Merges, reverts and cherry-picks keep git's message. A hook error is a warning, and the commit goes on.

The full description is in the architecture guide.