メニュー
Use when README.md may be stale relative to package.json scripts, Makefile targets, .nvmrc, or the user-visible UI. Discovers commits that touched those sources of truth since the skill last ran and merges the current values back into README.md.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use whenever you are iterating on the look or layout of a screen — tuning a CSS rule, building a new modal, redesigning a table, hunting a mobile-only regression. Walks an edit / reload / screenshot / inspect loop that uses the Read tool to view PNGs inline at every viewport (desktop, mobile, mobile-landscape, tablet). The harness drives the app through reusable flows (sign in, add sheet, add account, swipe a row) so each iteration only changes the bit that's being designed. Manual playbook — not part of the `maintenance` umbrella.
Use when the user wants to clear out the open Dependabot PRs — "do the dependabot PRs", "update the deps", "merge dependabot". Consolidates every open Dependabot bump into ONE branch + PR, resolves the peer-dependency fallout the bumps trigger (Vite / ESLint / TypeScript / React majors drag transitive tooling with them), gets the full CI chain green, then closes the superseded Dependabot PRs. Manual playbook — not part of the `maintenance` umbrella.
Use when src/data/achievements/catalog.ts is stale relative to a newly-shipped user-facing feature — or when a fresh achievement needs to be added, a trigger predicate rewritten, or the AchievementsModal chrome touched. The achievements modal (src/components/AchievementsModal.tsx) is a fullscreen four-tier (Beginner → Intermediate → Pro → Expert) guided tour where every feature is also an unlockable trophy. This skill describes how to add a new achievement, how to slot it into the right tier, how to phrase it (in English AND Swedish), and how to wire its trigger so the unlock fires when the user does the thing.
Use when about to open a PR (or just after pushing one) to decide whether the change needs a `.changes/unreleased/<unix-ts>-<slug>.md` fragment. Resolves the latest `v*` tag, walks commits and existing fragments since, classifies the current change against the rules in AGENTS.md, and either writes a new fragment, folds the substance into an existing fragment, or labels the PR `no-changelog`.
Use when docs/ may be stale relative to src/ layout, the persisted-data shape, or the Makefile target table — or when the in-app privacy policy at src/components/PrivacyPage.tsx may be stale relative to the storage/encryption/Dropbox claims it restates. Discovers commits that touched those sources of truth since the skill last ran and merges the current shape back into docs/architecture.md, docs/getting-started.md, and the privacy page.
Use when the maintainer (or an agent acting on their behalf) wants to cut a new release of the Budget app. Walks the pre-flight checklist, dispatches the workflow, verifies the deploy, and links to the rollback recipe. Manual playbook — not part of the `maintenance` umbrella.
| name | update-readme |
| description | Use when README.md may be stale relative to package.json scripts, Makefile targets, .nvmrc, or the user-visible UI. Discovers commits that touched those sources of truth since the skill last ran and merges the current values back into README.md. |
README.md mirrors several pieces of state that live elsewhere in the
repo — the make target table, the Node prerequisite, the live-site
URL, the list of UI behaviours described under "Examples", the
"Documentation" link list, and the badge row. When any of those move
without README.md moving with them, the README starts lying.
This skill brings README.md back into sync with its sources of truth.
.agent/skills/update-readme/.last-updated holds the git commit hash
of the last successful run. Empty means "never run" — fall back to the
repository's initial commit:
BASELINE=$(cat .agent/skills/update-readme/.last-updated)
[ -z "$BASELINE" ] && BASELINE=$(git rev-list --max-parents=0 HEAD)
Compute the diff range since the baseline and inspect the files that the README depends on:
git log --oneline "$BASELINE"..HEAD -- Makefile package.json .nvmrc \
src/components docs/ public/CNAME vite.config.ts
git diff --name-only "$BASELINE"..HEAD
For every change in those paths, decide whether the README claim it mirrors is still accurate. Use the mapping table below.
| Source of truth | README section to update |
|---|---|
Makefile targets | "Usage" table |
package.json scripts | "Usage" table (only the targets make exposes) |
.nvmrc | "Prerequisites" — Node version line |
public/CNAME / vite.config.ts base | "Troubleshooting" — Pages deploy 404 note + live URL |
src/components/SheetView.tsx + peers | "Examples" — keep the per-row affordances description honest |
docs/ filenames | "Documentation" link list |
.github/workflows/*.yml | Badge row (only when a workflow is added or removed) |
LICENSE SPDX id | License badge + "License" section |
If a change in any of the source-of-truth files has no corresponding README claim, leave the README alone — not every source change needs to surface in the README.
Read BASELINE and run the discovery commands above.
Walk the mapping table; for each row where the source moved, edit the matching README section to reflect the current state.
Keep wording terse — README.md is not the place for design rationale
(that belongs in docs/architecture.md).
Run make fmt and make lint so formatting and link rot don't ride
along.
Rewrite the tracking file:
git rev-parse HEAD > .agent/skills/update-readme/.last-updated
make fmt-check and make lint pass..agent/skills/update-readme/.last-updated contains the current
HEAD.After a run: