Skip to content
pionus

Commit messages in your repo's style

One command writes the commit message from your staged diff and your history.

$curl -fsSL https://raw.githubusercontent.com/Lucas-BRT/pionus/main/install.sh | bash

Reads your history

The convention, scopes and ticket format come from your commit subjects.

The prepare-commit-msg hook fills the editor on every plain git commit.

$ pionus hook install
$ git add .
$ git commit
# the editor opens with the generated message

refactor(auth): move session handling into its own module

Runs on the hardware you have

Setup picks the fastest device in your machine. Fractions of seconds per message, with the model loaded:

CPU

Any x86_64 processor, Intel or AMD.

  • 2.0s on a Ryzen 5 5500

GPU

Integrated or Dedicated; Intel, AMD or NVIDIA.

  • 0.20s on an RTX 3050 with Ryzen 5 5500

NPU

The AI chip of Intel Core Ultra. Does not keep the model loaded yet.

  • 5.1s on a Core Ultra 5 225H

See details for: all the measurements and how each device is supported.

Nothing leaves your machine

  • Nothing to sign up for

    No account, no API key, no subscription.

  • A small model

    A 1.1 GB download that runs on your hardware.

  • Offline to write

    Download once, run anywhere.

How a message is made

The full pipeline
  1. 1Read gitThe log, the branch and the staged diff.
  2. 2Infer the styleConvention, scopes and ticket format from the commit subjects.
  3. 3Fit the diffFiles are ranked into the model's token budget.
  4. 4Ask the modelGreedy decoding, on the fastest device.
  5. 5Clean upA bad reply is retried once, then falls back to the file list.