Engineering
Pull request reviewer
Reviews every pull request against your conventions, leaves inline comments, and posts a weekly digest of review load and CI health.
The prompt
This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
When a pull request is opened or updated against main, read the full diff. Read CONTRIBUTING.md and the last twenty merged pull request reviews so you know what this team actually cares about. Check out the code and run the linter and the type checker. Leave a review with inline comments only where you found something concrete: an unhandled error path, a duplicated helper, a missing test for a new branch, a migration that is not backward compatible. Skip style nits the formatter already handles. If the change looks good, approve it with a one-line summary. Post a link to your review in #eng and tag the author.
Trigger
What starts this agent
Runs when the event fires in the connected service. Filter on the fields that matter so only the runs you want wake the agent.
Example output
What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
Review posted on PR #2841
- Flagged an unhandled error path in `sync.ts:142`
- Suggested reusing `parseCursor` instead of a second parser
- Confirmed the migration is backward compatible
New to Helios? Start with Run your first agent.
Use cases
The task behind this template
PR review & digest
An agent reads each diff against your conventions and leaves a real review. A second agent summarizes the week: what merged, what is waiting, and how CI is holding up.
Incident summaries
An agent reconstructs the timeline from your incident channel and the deploys around it, identifies the triggering change, and drafts the write-up with the facts already assembled.
Weekly digests
An agent reads a week of activity across the tools your team uses, separates decisions from chatter, and posts a digest people actually read.
Related templates
Pair it with these
Engineering
Standup without the meeting
Reads yesterday's commits, merges, and review queue, then posts a standup so nobody has to attend one.
Engineering
Release notes writer
Turns a new tag into release notes grouped by theme, publishes them on GitHub, and files a changelog entry in Notion.
Engineering
Incident postmortem drafter
Reconstructs the incident timeline from Slack and GitHub, names the triggering change, and drafts the write-up in Notion.
Run Pull request reviewer on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.