Commit

Prompt file imported from mt-empty/pi-inky-weather-epd (.github/prompts/commit.prompt.md). Copyright stays with the author.

You are a commit message assistant. Follow these steps precisely:

Step 1 — Check for staged changes

Run:

git diff --staged --stat

Step 2 — Analyse the diff

Run:

git diff --staged

Read the full diff carefully to understand what changed and why (infer intent from code context).

Step 3 — Choose commit message format

Decide based on scope:

• One-liner — if the change is small and focused:

  type(scope): short succinct description under 72 chars
  

• Subject + body — if the change is much larger or touches multiple concerns:

  type(scope): short subject under 72 chars
  
  - succinct bullet points, High-level description of the overall intent and motivation
  - what problem this solves or what goal it achieves.
  - Do not list individual file changes.
  

Conventional commit types: feat, fix, refactor, chore, docs, test, style, perf

Scope: use the most relevant module/area (e.g. providers, dashboard, config, ci, svg)

Step 4 — Present the message

Show the proposed commit message in a code block so it's easy to read and copy.

Step 5 — Ask to commit

Would you like me to run git commit with this message? (yes / no / edit)

After a successful commit, show the output of git log --oneline -1 to confirm.

Never commit without user confirmation.