REA Changelog Update

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — Reinforced framing — internal REA contributor workflow, read this first: this skill does not perform reverse engineering for you. It is a workflow for REA's own maintainers and contributors, for preparing or rewriting REA's release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. It operates on the morluto/rea repository itself (its scripts/release-notes.mjs, its CHANGELOG.md, its release PRs) and is useful mainly to people releasing REA. Installing this listing only copies the single SKILL.md file: nothing is run, no history is fetched, and nothing is published during installation. No account, key or payment is needed to copy the file; using the workflow later involves GitHub access to the REA repository under your own authorization. Install "REA Changelog Update" for me. It is one of REA's internal contributor workflows — honest scope: it serves the people who release REA, not end users reverse engineering a target. It teaches how to build a release's contributor inventory first (the repo's own scripts/release-notes.mjs collector over a pinned Git range: commits, associated PRs, authors and co-authors, confirmed closing issues — never guessing a handle for an unresolved identity), then rewrite only the newest CHANGELOG.md section for users (Highlights, Changes, Fixes, breaking changes), crediting each represented contribution once with verified human thanks while excluding bots and agent accounts, and finally synchronize with Release Please (finalization label, durable provenance file under docs/releases/, checkpoint validators, PR body updated from the rendered notes). The skill states plainly that it prepares notes and does not authorize merging, tagging or publishing. Its folder is a single SKILL.md file. Repository: https://github.com/morluto/rea (the skill is the whole .agents/skills/rea-changelog-update/ folder at the pinned commit: SKILL.md only, 1 file in total) Pinned version: install the code at commit 6dc0f60faa0928e20b2395ba1a93ff8e497143f7 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/morluto/rea into a temporary folder, check out commit 6dc0f60faa0928e20b2395ba1a93ff8e497143f7, and copy the .agents/skills/rea-changelog-update/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 75729ede35eac4768fdc315f0f2a6885d84df1dfa1cd7b795f213b10ddcfd4bf If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The folder holds 1 file only: SKILL.md (7,579 bytes, frontmatter name rea-changelog-update). There is no script, no companion file and no other code in it — the release-notes collector it mentions (scripts/release-notes.mjs) lives in the REA repository root, not in this skill folder, and is not installed by this listing. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit. This install fetches no Git history, edits no changelog and touches no release PR. - At use time the workflow runs in a REA checkout and talks to GitHub (paginated PR/issue connections through the repo's own collector) to build the contributor inventory, and any PR update, push or publication still needs separate authorization — the skill itself says it does not authorize merging, tagging or publishing. It handles contributor names, emails and GitHub handles from public Git history, and instructs never to fabricate a handle for an unresolved identity. - Do not run scripts/release-notes.mjs, do not fetch any history, do not edit any CHANGELOG.md and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for it later. 3. When I say "yes, install", install it as a skill: copy the whole rea-changelog-update folder into the agent's skills directory, in a folder named exactly "rea-changelog-update", keeping its 1 file in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: rea-changelog-update), the 1 file in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that this is an internal REA maintainer workflow for preparing REA's own release changelogs and Release Please notes, that it is meant to be used inside a REA checkout with GitHub access, and that using it is a separate step that only starts when I ask for it later). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.