# Check Changes

> >

- **Type:** Skill
- **Install:** `agentstack add skill-lorem-dev-skillkeeper-check-changes`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [lorem-dev](https://agentstack.voostack.com/s/lorem-dev)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** Apache-2.0
- **Upstream author:** [lorem-dev](https://github.com/lorem-dev)
- **Source:** https://github.com/lorem-dev/skillkeeper/tree/main/.agents/skills/check-changes
- **Website:** https://lorem-dev.github.io/skillkeeper/

## Install

```sh
agentstack add skill-lorem-dev-skillkeeper-check-changes
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# check-changes

Verify that `CHANGES.md` is current with the commit history since the last
release.

## Steps

1. **Find the last release boundary.**
   Run `git log --oneline` and locate the most recent release commit (a commit
   whose message starts with `release:` -- the prefix the `bump-version` skill
   uses, e.g. `release: 0.1.0-rc.1` -- or a version tag such as `v1.0.0`).
   If no release commit exists yet, the boundary is the initial commit.

2. **Collect commits since that boundary.**

   ```bash
   git log --oneline ..HEAD
   ```

   Exclude pure merge commits and chore/ci/build commits that do not represent
   user-visible changes (they do not require changelog entries, but note them).

3. **Read the Development section of CHANGES.md.**
   Open `CHANGES.md` and extract every bullet under `## Development`.

4. **Cross-reference.**
   For each commit that represents a user-visible change (type `feat`, `fix`,
   `refactor`, or `perf`), check whether a corresponding bullet exists in the
   Development section. A bullet does not need to quote the commit message
   verbatim -- it only needs to describe the same change at a short summary
   level.

5. **Report findings.**
   - List commits with NO changelog entry (missing entries -- these must be
     added).
   - List changelog bullets that appear to describe nothing in the commit
     history (stale or speculative entries -- flag for author review).
   - If everything matches, report "CHANGES.md is current."

6. **Do not edit CHANGES.md automatically.**
   Propose the missing bullets in your report and let the developer apply them.
   The developer owns the changelog wording.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [lorem-dev](https://github.com/lorem-dev)
- **Source:** [lorem-dev/skillkeeper](https://github.com/lorem-dev/skillkeeper)
- **License:** Apache-2.0
- **Homepage:** https://lorem-dev.github.io/skillkeeper/

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-lorem-dev-skillkeeper-check-changes
- Seller: https://agentstack.voostack.com/s/lorem-dev
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.