You can customize the format of Slack messages sent by Ellipsis using markdown. We recommend you provide a markdown template in your React Workflow and Cron Workflow instructions to Ellipsis, as well as a few examples. Here are some examples of how to customize Slack messages.
The above React Workflow includes metadata like lines added/removed, and the author of the PR.
The above React Workflow includes a fully custom template explaining what the feature launch is about.
And finally, this customer asked Ellipsis to make a sarcastic joke about their pull request. Or maybe Ellipsis is always that snarky… If you don’t provide a template in your workflow instructions, Ellipsis will use a default template which looks something like: 
Whenever a PR is merged, post a summary to #engineering with a message like this:

[{PR number}]({link to PR}) by {PR author} was merged into {PR repository name} ({PR title})
- {bullet point with most important change 1}
- {bullet point with most important change 2}
- {... repeat for up to 8 bullet points}

Here is an example message:

[#4502](https://github.com/ellipsis-dev/ellipsis/pull/4502) by hbrooks was merged into ellipsis (refactor of WorkflowStatus enum)
- Set job_run status to PROCESSING for scheduled job runs instead of no-op
- Reset job run output by clearing status_reason before processing
- Update status to PROCESSING before persisting changes
- Ensure proper job run update by capturing return values from update_cron_job_run calls
- Set job_run status to DONE after agent processing completes</CodeBlock>
You’d then see messages that look like this:

Start a free trial

Click here to start a free 7 day trial of AI Code Reviews & Bug Fixes