AutoDoc ran on Lurnby — here's what it would generate
Hi! I'm Mike from Paprika Labs. We're running a paid pilot of AutoDoc — a GitHub Action that automatically generates PR documentation from diffs on every merge.
I noticed this repo no ADR directory, no CHANGELOG — the kind of documentation gap AutoDoc fills automatically.
I ran AutoDoc on your last 3 merged PRs to show you what it produces:
PR #75: Preact app frontend
Merged 2026-01-29 · undefined files changed (+undefined -undefined)
PR Summary (auto-generated)
This PR introduces pagination and filters for the Preact app frontend, allowing users to navigate between pages and filter articles using browser navigation. Changes include updating the article query maker to handle pagination and filters, modifying the article model to remove legacy highlight spans, and updating the client-side code to use URL-synced pagination and filters.
Architecture Note (auto-generated)
Minor change — no ADR needed.
PR #74: Preact app frontend
Merged 2026-01-29 · undefined files changed (+undefined -undefined)
PR Summary (auto-generated)
This PR introduces the full Reader functionality for the Preact app frontend. Specifically, it adds the ability to update article content and reanchor highlights. The changes include updating the update_article function to build the content tree and reanchor highlights when content is updated, adding a new filter_by_article function to the highlight_query_maker module, and modifying the get_highlights function in the highlights module to filter by article UUID. Additionally, the Article model has been updated to include a method to build the content tree on-demand.
Architecture Note (auto-generated)
Minor change — no ADR needed.
PR #73: Add start/end offset columns to Highlight model
Merged 2026-01-24 · undefined files changed (+undefined -undefined)
PR Summary (auto-generated)
The PR #73 added start and end integer columns to the Highlight model, using SQLAlchemy 2.0 mapped_column syntax, and dropped the unused position column. It also included start/end in the to_dict() API response, backfilled null UUIDs, and fixed tests to provide required user_id for highlights.
Architecture Note (auto-generated)
Minor change — no ADR needed.
What AutoDoc does
AutoDoc installs as a GitHub Action. Every time a PR is merged, it reads the diff and generates:
- A structured PR summary (what changed and why)
- An Architecture Decision Record note (when there's a meaningful design decision)
- Changelog entries ready to copy into your CHANGELOG
Zero manual input. Zero context-switching. The docs are there by the time the merge lands.
Install: github.com/paprika-org/autodoc
Landing page: autodoc.paprika-labs.app
Does this look useful for Lurnby? Happy to answer questions or customise the output format for your team's conventions.
If this isn't relevant to your project, feel free to close the issue. Sorry for the noise.
AutoDoc ran on
Lurnby— here's what it would generateHi! I'm Mike from Paprika Labs. We're running a paid pilot of AutoDoc — a GitHub Action that automatically generates PR documentation from diffs on every merge.
I noticed this repo no ADR directory, no CHANGELOG — the kind of documentation gap AutoDoc fills automatically.
I ran AutoDoc on your last 3 merged PRs to show you what it produces:
PR #75: Preact app frontend
Merged 2026-01-29 · undefined files changed (+undefined -undefined)
PR Summary (auto-generated)
This PR introduces pagination and filters for the Preact app frontend, allowing users to navigate between pages and filter articles using browser navigation. Changes include updating the article query maker to handle pagination and filters, modifying the article model to remove legacy highlight spans, and updating the client-side code to use URL-synced pagination and filters.
Architecture Note (auto-generated)
Minor change — no ADR needed.
PR #74: Preact app frontend
Merged 2026-01-29 · undefined files changed (+undefined -undefined)
PR Summary (auto-generated)
This PR introduces the full Reader functionality for the Preact app frontend. Specifically, it adds the ability to update article content and reanchor highlights. The changes include updating the
update_articlefunction to build the content tree and reanchor highlights when content is updated, adding a newfilter_by_articlefunction to thehighlight_query_makermodule, and modifying theget_highlightsfunction in thehighlightsmodule to filter by article UUID. Additionally, theArticlemodel has been updated to include a method to build the content tree on-demand.Architecture Note (auto-generated)
Minor change — no ADR needed.
PR #73: Add start/end offset columns to Highlight model
Merged 2026-01-24 · undefined files changed (+undefined -undefined)
PR Summary (auto-generated)
The PR #73 added start and end integer columns to the Highlight model, using SQLAlchemy 2.0 mapped_column syntax, and dropped the unused position column. It also included start/end in the to_dict() API response, backfilled null UUIDs, and fixed tests to provide required user_id for highlights.
Architecture Note (auto-generated)
Minor change — no ADR needed.
What AutoDoc does
AutoDoc installs as a GitHub Action. Every time a PR is merged, it reads the diff and generates:
Zero manual input. Zero context-switching. The docs are there by the time the merge lands.
Install: github.com/paprika-org/autodoc
Landing page: autodoc.paprika-labs.app
Does this look useful for
Lurnby? Happy to answer questions or customise the output format for your team's conventions.If this isn't relevant to your project, feel free to close the issue. Sorry for the noise.