メニュー
Compatibility inventory workflow for OpenReader vs reader-dev. Use before implementing or changing any OpenReader feature that exists in upstream reader-dev; this skill analyzes and documents differences without editing code.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | readerdev-compat-inventory |
| description | Compatibility inventory workflow for OpenReader vs reader-dev. Use before implementing or changing any OpenReader feature that exists in upstream reader-dev; this skill analyzes and documents differences without editing code. |
Use this skill before code changes for upstream-backed features.
Do not edit application code while using this skill. Produce or update a compatibility matrix first.
must-fix;acceptable-change;intentional-redesign;unknown.Update:
docs/compat/reader-dev-openreader-gap-analysis.md
For large modules, create a focused file under docs/compat/.
API compatibility workflow for OpenReader. Use when changing routes, Gin handlers, auth, request bodies, query parameters, response schemas, status codes, API errors, or frontend API clients.
Book source and parser compatibility workflow for OpenReader. Use when changing online sources, CSS selectors, XPath-like rules, RSS, chapter parsing, content cleaning, import preview/import, or local book parsing.
Data compatibility workflow for OpenReader. Use when changing GORM models, SQLite migrations, cache, library, uploads, local store, backup/restore, WebDAV storage, or persistent settings.
Frontend UX compatibility workflow for OpenReader. Use when changing Vue pages, routing, Pinia stores, reader UI, bookshelf, settings, import, WebDAV, sidebars, touch gestures, keyboard handling, or local persisted state.
Backend architecture guardrails for OpenReader Go/Gin/GORM/SQLite changes. Use when modifying handlers, services, models, migrations, WebSocket sync, WebDAV, backup, imports, cache, or any backend API behavior.
Local Docker release workflow for OpenReader. Use before building or publishing GHCR images, tagging releases, validating image metadata, or reporting Docker release progress.