LobstackEngineering · Asks before everything
On call
Reads new errors, groups the ones that are the same bug, and names the change that caused them.
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
Incident postmortem
Write a blameless postmortem from an incident's alerts, logs and chat: timeline, impact, root cause, and actions with owners.
SKILL.md · App
On a schedule, and whenever you ask.
Every weekday at 9am
Morning error digest
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
Everything while you are there: it ships asking first
02
Deploying, rolling back or resolving: never its call
Real files in your Library, not just replies.
- Documents
- Diagrams
- Code and pull requests
- 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