How to use the Commit Message Generator.
A commit message should summarize the actual diff and why it matters. Avoid claiming tests or fixes that are not present in the supplied changes.
Make the workflow fit your task.
Read the actual diff and identify the main behavior change and its reason. Write a concise subject and add context where useful, excluding claims about tests, fixes or scope absent from the evidence.
- What you provide
- Actual code diff.
- What you get
- Concise accurate commit message.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Diff adds a missing-label warning to a form checker.
Completed example
Add missing-label warnings to the form checker.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should a commit message claim tests passed when no test result is supplied?
No. Mention only verified testing or leave that claim out. The message should reflect the evidence available for the change.
Why does the message describe implementation details but miss the purpose?
Explain what changed for the user or maintainer, then add technical detail only where it clarifies the reason.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑