For reviews, docs, and teams.
Keep the useful detail. Skip the running commentary of the agent.
Review the change.
Keep comments short and PR bodies in a structure, so that a reviewer finds what changed.
See the core checksgh pr create --title "Round invoice totals" --body
This PR rounds invoice totals to whole cents. It also updates the tests.
The rounding now happens once, at the end.
Overall, this change makes billing more reliable and robust.[concise] PR/issue body is too verbose: 3 prose paragraphs (limit 1), use short bullets instead. Use a short "## Summary" bullet list instead of prose paragraphs.Write docs in your voice.
Turn on the writing checks for stock phrases, unnecessary qualifiers, and canned conclusions. Start with the technical preset.
Choose a writing presetWrite docs/billing.md
[concise] AI writing patterns in ~/code/billing-api/docs/billing.md: line 3 "delves" (vocabulary: look at, examine); line 3 "game-changer" (inflation: state what changed); line 5 "In conclusion" (closers: cut, end on the last fact). Rewrite them. …
To keep it, send the identical write again to confirm. …Share your house rules.
Commit the project configuration. Add custom pattern packs for the words that your team does not want.
Create a custom pack
Set up cloud agents.
A cloud agent often starts from a fresh checkout with no configuration file. Set the configuration in environment variables. Soft fail flags findings and does not block.
Read the cloud recipesexport BEC_FEATURE_ENABLE=emDash,aiWriting
export BEC_ENABLE_PATTERNS=file-narration,benefit-tail
export BEC_HOOK_SOFT_FAIL=1
export BEC_LOG_ENABLED=1Write docs/billing.md
[concise] soft-fail: AI writing patterns in ~/code/billing-api/docs/billing.md: line 3 "delves" (vocabulary: look at, examine). Rewrite them. …