Skip to content
SkillCheatSheet Sign in

rea-changelog-update

An AI agent skill from morluto/rea, scored 59 out of 100 by code.

59/ 100C

Code score by group

  • Spec20/20
  • Description7/20
  • Procedure7/15
  • Done criteria0/15
  • Resources8/10
  • Scripts5/8
  • Safety7/7
  • Upkeep5/5

It loses the most points in Done criteria (15), the group that checks whether there is a checklist and a step that verifies the work.

What the author says it does

Prepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.

This is the description in the skill's own SKILL.md, written by its author, not by SkillCheatSheet.

Repository
morluto/rea
Folder
.agents/skills/rea-changelog-update
License
MIT
GitHub stars
453,855
SKILL.md lines
136
Other files
0

Add rea-changelog-update to your agent

npx skills add morluto/rea --skill rea-changelog-update

The command uses the open skills CLI. A skill is instructions and scripts your agent will follow, so read it first: open the folder on GitHub at the commit that was scored.

More skills from morluto/rea

  1. rea-analysis-optimization

    Optimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache…

    57C
  2. reverse-engineer-anything

    Reverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a…

    56C
  3. rea-ci-tests-audit

    Audit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than o…

    54D
  4. rea-tool-design

    Audit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.

    49D

All skills in morluto/rea

Scores come from a snapshot of 300 public GitHub repositories taken on 12 November 2026. Every score is the result of fixed checks run by code; no AI is involved. How scoring works.