Menu
Maintain CHANGELOG.md for the @zeix/cause-effect library. Use after meaningful code changes, when asked to add release notes, or to prepare a release.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Shared reference knowledge base for @zeix/cause-effect agent skills. Contains common reference files used by multiple skills to avoid duplication.
Maintains Architectural Decision Records (ADRs) for this project. Creates, updates, lists, and supersedes ADRs in the /adr/ directory.
Expert guidance for using the @zeix/cause-effect reactive signals library in any project. Use when implementing reactive patterns, debugging unexpected behavior, or answering questions about the public API, signal types, or design decisions. Works in any project that depends on @zeix/cause-effect — all knowledge is embedded, no library source required.
Sparring partner for design and planning. Asks critical questions, researches feasibility, weighs tradeoffs, and produces or updates REQUIREMENTS.md, ARCHITECTURE.md, and TODO.md. Also triages GitHub issues and bug reports into actionable tasks.
Expert developer for the @zeix/cause-effect reactive signals library. Use when implementing features, fixing bugs, writing tests, or answering questions about the library's internals, public API, or design decisions.
Keep developer-facing documents up to date with the @zeix/cause-effect source code: README.md, GUIDE.md, ARCHITECTURE.md, REQUIREMENTS.md, AGENTS.md, .github/copilot-instructions.md, and JSDoc in src/. Use after code changes, to verify consistency, or to update a specific document.
| name | changelog-keeper |
| description | Maintain CHANGELOG.md for the @zeix/cause-effect library. Use after meaningful code changes, when asked to add release notes, or to prepare a release. |
| user_invocable | true |
# Changelog
## [Unreleased] ← only present when unreleased changes exist
### Added
### Fixed
## 1.0.0 ← released versions use bare version numbers, no brackets
### Changed
...
## [Unreleased] is only present when there are documented changes not yet released.
Create it at the top (below # Changelog) when documenting the first new change after a release.
It does not exist between releases.## 1.0.0, ## 0.18.5, etc. No brackets.### Added, ### Changed, etc.) that have entries.## 0.18.0 is the baseline. Do not document changes before it.
<adding_entries>
CHANGELOG.md.git diff main..HEAD -- src/ index.ts or as directed.## [Unreleased] section, create one immediately below # Changelog.<preparing_a_release> When asked to release a version:
## [Unreleased] to ## X.Y.Z — do not leave an empty [Unreleased] section behind.version in package.json to match.@version tag in index.ts to match.
</preparing_a_release><entry_style>
- **\createMemo` `watched` option**: description…`