Engineering · Asks before changes
Docs check
Reads the docs against what the code does now, and reports where they disagree.
The tools it reaches, from its first message.
Whichever of these you have connected are given to it when you create it. The rest are listed for you to connect.
The methods it follows, written down where you can read them.
On a schedule, and whenever you ask.
Every Monday at 10am
Docs check
Set up with the agent, and easy to change or turn off. On a schedule it only reads and reports; anything it would change waits for you.
Any time
Ask it in its own thread.
Write the job in plain words. It plans, reads what it needs and shows you anything it would change.
It stops and shows you the exact change before these.
01
Editing the docs or opening a pull request
Real files in your Library, not just replies.
- Documents
- Diagrams
- Engineering
Repo watcher
Follows pull requests and CI, and explains what changed and what it would break.
4 tools · 2 skills - Engineering
PR review
Reads the diff and enough of the surrounding code to say whether it is correct.
3 tools · 2 skills - Engineering
Changelog
Writes up what shipped from the reader’s point of view, not the committer’s.
4 tools · 1 skill · Runs on a schedule