القائمة
Use when README.md may be stale. Discovers commits since the last README update, identifies what changed, and merges updates into README.md.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the user wants to add, update, or remove entries in the CV (src/data/cv.json), or wants recommendations on what to add, remove, or emphasize. Always validates the result against schemas/cv.schema.json before finishing.
Use when the Visual workflow (.github/workflows/visual.yml) is failing on `main` or on a PR. Reproduces the failure, identifies which commit broke each snapshot, decides whether the diff is intentional, re-records baselines if so, and commits the new pixels.
Use when the user wants to clean up the open Dependabot PR queue. Walks the open Dependabot PRs newest-first, merges the green ones, then rebases and fixes the CI-failing ones, pushes, waits for CI, and merges.
Use to bring the whole repo back in sync after a batch of changes. Routes to every update-* skill in deterministic order and aggregates the resulting diff.
Use when this repo may have drifted out of conformance with OSS_SPEC.md. Runs the bash mirror of the oss-spec validator (no Rust toolchain required), walks the violations, and fixes each one until the validator reports zero violations.
Use when the user wants to refresh the `tagline` and/or `description` of one or more companies in `src/data/cv.json` using their declared `sourceUrls`. Fetches each source, synthesizes a tight bilingual tagline + description pair, propagates the change into any matching `experience[].printDescription` (and assignment `printDescription` when the assignment's `clientId` resolves to a company being refreshed), and validates the result.
| name | update-readme |
| description | Use when README.md may be stale. Discovers commits since the last README update, identifies what changed, and merges updates into README.md. |
Bring README.md back in sync with the sources of truth in the repo.
The sibling file .last-updated holds the git commit hash of the last
successful run. An empty file means "never run" — use the initial commit
as the baseline.
Determine what has changed since the baseline:
BASE=$(cat .agent/skills/update-readme/.last-updated)
HEAD=$(git rev-parse HEAD)
git log --oneline "${BASE:-$(git rev-list --max-parents=0 HEAD)}..$HEAD"
git diff --name-only "${BASE:-$(git rev-list --max-parents=0 HEAD)}..$HEAD"
| Source of truth | README section |
|---|---|
package.json scripts | Scripts |
Makefile targets | Scripts / Build |
src/ top-level layout | Structure |
src/data/cv.json | (site content — README blurb) |
src/data/cv.types.ts | (type contract — README blurb) |
schemas/cv.schema.json | Why / Configuration |
.github/workflows/*.yml | Badges, CI section |
OSS_SPEC.md presence | Links / Contributing |
npm run / make target a contributor
would want, with a one-line description each.src/ layout..github/workflows/ci.yml.README.md end-to-end and check each section against the
mapping table.make fmt-check so any prose formatting is consistent.If you discover a drift pattern not already in the mapping table (e.g. a new source file whose contents the README should restate), append a row to the table and commit the skill update alongside the README change.