update-readme

Estrelas8

Forks0

Atualizado3 de junho de 2026 às 13:02

Bring README.md's Features and Tech Stack sections up to date with the actual feature modules, libraries, and recent work.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

CinqueIzumi

CinqueIzumi/Softcover

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	update-readme
description	Bring README.md's Features and Tech Stack sections up to date with the actual feature modules, libraries, and recent work.

Keep README.md in sync with what the app actually ships — both the Features section (against the feature modules) and the Tech Stack section (against the version catalog) — so the README never goes stale. README only — do not commit.

Steps:

Use the Bash tool to list the directories under feature/ — this is the source of truth for what features exist.
Read the Features section of README.md (grouped by user-facing area: Library, Reading, Explore, Book Details, Profile, Settings). Use the Bash tool to run git log since the last release tag/version to see what changed recently.
Compare: find features present in the code (or recent commits) that are missing or described inaccurately in the README.
Use the Edit tool to update the Features section. Keep the existing editorial grouping and tone, and add or adjust only what changed — do not rewrite sections that are still accurate. Preserve the heading structure and the Table of Contents.
Read gradle/libs.versions.toml — the source of truth for libraries and their versions. Compare it against the Tech Stack tables in the README. Use the Edit tool to:
- Correct any version string that has drifted.
- Add a row for any library that is now in the catalog (and meaningfully part of the stack) but missing from the tables, placing it in the right table (Core, Data & Networking, App Architecture, Testing) and matching the existing row format.
- Remove rows for libraries that have been dropped from the catalog. Keep the tables' existing structure and column layout.
Report a short summary of what changed (features + tech stack).

Do not create a commit. Do not modify anything outside README.md.

Mais deste repositório

mesmo repositório

release

CinqueIzumi/Softcover

Prepare a release — refresh the README, run all checks, then set the new versionName across all platforms (Android/iOS/desktop) and bump the build number. Stops with changes unstaged; never commits or tags.

2026-06-178

increment-version-code

CinqueIzumi/Softcover

Increment the app's build number by 1 — Android versionCode in app/build.gradle.kts and iOS CURRENT_PROJECT_VERSION in iosApp/iosApp.xcodeproj/project.pbxproj. Desktop has no build-number field, so it is unaffected.

2026-06-148

set-version-name

CinqueIzumi/Softcover

Set the app's version name to the given value on all platforms — Android versionName in app/build.gradle.kts, iOS MARKETING_VERSION in iosApp/iosApp.xcodeproj/project.pbxproj, and desktop packageVersion in desktopApp/build.gradle.kts — and bump the build number by 1.

2026-06-148

style-check

CinqueIzumi/Softcover

Auto-fix mechanizable style, then run every verification gate (ktlint, detekt, lint, module graph, dependency analysis, mechanical style checks).

2026-06-038

name	update-readme
description	Bring README.md's Features and Tech Stack sections up to date with the actual feature modules, libraries, and recent work.

Steps:

Use the Bash tool to list the directories under feature/ — this is the source of truth for what features exist.
Read the Features section of README.md (grouped by user-facing area: Library, Reading, Explore, Book Details, Profile, Settings). Use the Bash tool to run git log since the last release tag/version to see what changed recently.
Compare: find features present in the code (or recent commits) that are missing or described inaccurately in the README.
Use the Edit tool to update the Features section. Keep the existing editorial grouping and tone, and add or adjust only what changed — do not rewrite sections that are still accurate. Preserve the heading structure and the Table of Contents.
Read gradle/libs.versions.toml — the source of truth for libraries and their versions. Compare it against the Tech Stack tables in the README. Use the Edit tool to:
- Correct any version string that has drifted.
- Add a row for any library that is now in the catalog (and meaningfully part of the stack) but missing from the tables, placing it in the right table (Core, Data & Networking, App Architecture, Testing) and matching the existing row format.
- Remove rows for libraries that have been dropped from the catalog. Keep the tables' existing structure and column layout.
Report a short summary of what changed (features + tech stack).

Do not create a commit. Do not modify anything outside README.md.