AutoDoc ran on mports — here's what it would generate
Hi! I'm Mike from Paprika Labs. AutoDoc is a GitHub Action that generates PR documentation from diffs on every merge — free for public repos.
I noticed this repo has 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 #612: cleanup: Sort SUBDIR entries in category Makefiles
Merged 2026-06-06
PR Summary (auto-generated)
Sort and normalize SUBDIR entries across multiple category Makefiles to keep ports listed in ASCII order and consolidate previously trailing entries into the main lists.
Architecture Note (auto-generated)
Minor change — no ADR needed.
PR #611: Fix key name for Claude Code Review action
Merged 2026-06-05
PR Summary (auto-generated)
The PR fixes a naming inconsistency in the Claude Code Review GitHub Action. The input parameter name was changed from anthropic_api_key to claude_code_oauth_token to match the secret name CLAUDE_CODE_OAUTH_TOKEN. This change ensures the action uses the correct authentication token.
Architecture Note (auto-generated)
Minor change — no ADR needed.
PR #610: textproc/iso8879: Fix build failure by using USES=zip
Merged 2026-06-05
PR Summary (auto-generated)
The textproc/iso8879 port was updated to use the USES=zip framework, which resolves a build failure caused by missing /usr/local/bin/unzip during the fake stage. Additionally, the do-install target was simplified by removing redundant steps and using standard INSTALL_DATA.
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.
AutoDoc is free for public repos. Two-minute install:
uses: paprika-org/[email protected]
with:
openai_api_key: ${{ secrets.OPENAI_API_KEY }}
github_token: ${{ secrets.GITHUB_TOKEN }}
More info: autodoc.paprika-labs.app
Does this look useful for mports? Happy to answer questions or help with the install. Private-repo support and team analytics are on the roadmap ($39/repo/month when they ship).
If this isn't relevant to your project, feel free to close the issue. Sorry for the noise.
AutoDoc ran on
mports— here's what it would generateHi! I'm Mike from Paprika Labs. AutoDoc is a GitHub Action that generates PR documentation from diffs on every merge — free for public repos.
I noticed this repo has 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 #612: cleanup: Sort SUBDIR entries in category Makefiles
Merged 2026-06-06
PR Summary (auto-generated)
Sort and normalize SUBDIR entries across multiple category Makefiles to keep ports listed in ASCII order and consolidate previously trailing entries into the main lists.
Architecture Note (auto-generated)
Minor change — no ADR needed.
PR #611: Fix key name for Claude Code Review action
Merged 2026-06-05
PR Summary (auto-generated)
The PR fixes a naming inconsistency in the Claude Code Review GitHub Action. The input parameter name was changed from
anthropic_api_keytoclaude_code_oauth_tokento match the secret nameCLAUDE_CODE_OAUTH_TOKEN. This change ensures the action uses the correct authentication token.Architecture Note (auto-generated)
Minor change — no ADR needed.
PR #610: textproc/iso8879: Fix build failure by using USES=zip
Merged 2026-06-05
PR Summary (auto-generated)
The
textproc/iso8879port was updated to use theUSES=zipframework, which resolves a build failure caused by missing/usr/local/bin/unzipduring the fake stage. Additionally, thedo-installtarget was simplified by removing redundant steps and using standardINSTALL_DATA.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.
AutoDoc is free for public repos. Two-minute install:
More info: autodoc.paprika-labs.app
Does this look useful for
mports? Happy to answer questions or help with the install. Private-repo support and team analytics are on the roadmap ($39/repo/month when they ship).If this isn't relevant to your project, feel free to close the issue. Sorry for the noise.