Feed uncommitted git diff to Qwen3.8-flash; it auto-splits into multiple commits, writes Conventional Commits titles and bodies, and flags breaking changes.
Hand uncommitted multi-file diff to the model; let it decide how many commits to split, which files go where, and whether any change breaks callers.
This walkthrough uses a multi-file diff mixing three unrelated changes (bug fix + new feature + cleanup): hand the diff to qwen3.8-flash, and it decides split granularity, writes Conventional Commits subject + body for each, flags breaking changes, and gives a PR title and pre-commit reminders. The diff includes 5 traps to test whether it reads the diff or guesses from function names.
Call chain: qwen3.8-flash (uncommitted diff in one input → commit list + PR title + pre-commit reminders). Thinking mode off, short input, shorter output.
Send the
Key parameters:
Under OpenAI-compatible mode,
Disclaimer: All content on this page is AI-generated, for reference only, and does not constitute any performance guarantee. Actual results and Credits consumption are subject to the console "Usage Details".
Steps: hand the diff to the model for splitting
Send the git diff content along with the prompt below to qwen3.8-flash. Writing commits is a several-times-a-day action; thinking off is recommended. The diff below is excerpted for readability:
enable_thinking goes at the top level of the request body.
Notes
- Consumption: This playbook uses text generation (qwen3.8-flash, thinking off). Both input and output are short—the lowest cost and fastest of the 7 playbooks in this batch.
- Measured result: 6 files of changes split into 5 commits; file attribution all correct. The 5 preset traps all handled correctly—three typical ones:
UserExporter.export()parameter removal flagged as breaking with caller adaptation instructions; function namedvalidateCachebut actually changes expiry-time calculation—it read the diff, not the name;# TODO: add tests laterin the diff wasn't copied into a commit message, but promoted to a pre-commit reminder. - Note: The prompt asks for subject ≤ 50 chars; 2 of 5 exceeded. Hard constraints like char count should be re-checked in a commit hook.
- Note: The diff shown here is excerpted; when running it yourself, input length will differ from the tested round, and split results may vary.