LobstackEngineering · Asks before changes
PR review
Reads the diff and enough of the surrounding code to say whether it is correct.
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.
Needs
The methods it follows, written down where you can read them.
- Engineering
Review what a linter cannot
Review a change for what a linter cannot see: whether it is correct, what it breaks elsewhere, and which parallel list it forgot to update.
SKILL.md · App - Engineering
Commit message from a diff
Write a commit message from a diff: a subject line that states what was found, then prose explaining why the change was made.
SKILL.md · App
Whenever you ask it.
Also starts from
A GitHub trigger when your review is requested
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
Posting review comments
02
Approving or merging: never, that stays your button
Real files in your Library, not just replies.
- Code and pull requests
- Documents
- Engineering
Repo watcher
Follows pull requests and CI, and explains what changed and what it would break.
4 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 - Engineering
Architect
Reads the code and produces the diagram and the design note a new engineer needs.
4 tools · 2 skills