GitHub
VerifiedDeveloper: Lab24
About
Astell reads your repositories so the context your team ships is one question away. Ask what changed in a pull request, who last touched a file, or how a bug travels across services, and get an answer with links back to the source.
Common uses include drafting release notes from merged PRs, triaging open issues by module, tracing the history of a file, and onboarding engineers by walking them through a service end to end.
Repository scoping and branch protection stay in your hands. Astell only reads what your installation already allows.
Try asking
Summarize 482 and flag breaking changes for downstream services.
Draft release notes from every PR merged into main in the last 2 weeks, grouped by area.
Group open issues labeled bug by affected module and link the #customer-support Slack thread where each was reported.
Who last touched auth/session.ts and what PR introduced the latest change?
For each PR merged in the last week, link the Notion spec it implements and call out drift.
