skill-lorem-dev-skillkeeper-check-changes · by Install
$ agentstack add skill-lorem-dev-skillkeeper-check-changes ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-lorem-dev-skillkeeper-check-changes) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
check-changes
Verify that CHANGES.md is current with the commit history since the last release.
Steps
- 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.
- 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).
- Read the Development section of CHANGES.md.
Open CHANGES.md and extract every bullet under ## Development.
- 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.
- 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."
- 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
- Source: 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.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.