LobstackEngineering · Asks before changes
Repo watcher
Follows pull requests and CI, and explains what changed and what it would break.
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
Triage a failing build
Triage a red CI run: find the first real failure, attribute it to a change, and say whether the code is wrong or the runner was.
SKILL.md · App - Engineering
Pull request description
Write a pull request description from the diff: why it exists, what changed, how it was tested, and where a reviewer should look first.
SKILL.md · App
Whenever you ask it.
Also starts from
A GitHub trigger: a failed CI run or a review requested (Triggers → GitHub)
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
Pushing a branch or opening a pull request
02
Running commands
Real files in your Library, not just replies.
- Code and pull requests
- Diagrams
- Documents
- 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 - Engineering
Architect
Reads the code and produces the diagram and the design note a new engineer needs.
4 tools · 2 skills