What is after-changes?

A checklist for finishing a set of code changes. It reviews the code, checks whether the README still matches the project, and creates a Git commit.

Use it after editing code when you need a review, README consistency check, and commit.

It helps catch leftover issues and outdated documentation before the changes are recorded in version control.

How Jessinra/Lorekeeper configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Jessinra/Lorekeeper. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Jessinra/Lorekeeper/main/.claude/skills/after-changes/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/Jessinra/Lorekeeper

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jessinra/lorekeeper/after-changes/github.svg)](https://agentmods.dev/skills/jessinra/lorekeeper/after-changes)

Your own site

<a href="https://agentmods.dev/skills/jessinra/lorekeeper/after-changes"><img src="https://agentmods.dev/badge/skills/jessinra/lorekeeper/after-changes/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jessinra/lorekeeper/after-changes"><img src="https://agentmods.dev/badge/skills/jessinra/lorekeeper/after-changes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 85 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 559 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00085	$0.00559
Opus 5.5	$0.00034	$0.00224
Sonnet 5.5	$0.00017	$0.00112
Haiku 4.5	$0.00009	$0.00056

Measured 1mo ago against content hash e461bb37ab42, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

after-changes scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/after-changes/SKILL.md · 52 lines

What it actually says

After-Changes Checklist

Run these three steps in sequence after every set of code changes.

Step 1 — Code Review

Run the /simplify skill. Wait for it to complete and apply all fixes before moving on.

Step 2 — README Check

Run git diff HEAD (or git diff HEAD~1 if already staged/committed) to get the full list of changed files and what changed.
Read README.md.
For each changed file, check: does the README make a claim about this file, its API, its behaviour, or its config that is now stale?
Common staleness patterns:
- New env vars / config keys not in the config table
- API endpoints added, removed, or renamed
- New UI tabs, features, or workflows not described
- Architecture claims that no longer match the code
- "Cannot do X" statements that are now wrong
If anything is stale or missing, update README.md in-place. Keep changes minimal — add what's missing, fix what's wrong, remove nothing that's still true.
If README is already accurate, say so and skip.

Step 3 — Commit

Run git status and git diff HEAD to review everything that will be committed.
Stage all relevant changed files (be explicit — avoid git add -A).

Write a commit message following this format:

<type>(<scope>): <short summary under 72 chars>

- bullet for each logical change
- explain WHY for non-obvious changes

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>

Types: feat, fix, refactor, docs, chore, test

Confirm the commit hash and summary.

Notes

If Step 1 (simplify) finds and fixes issues, re-check README in Step 2 for any new staleness those fixes introduced.
If there is nothing to commit (working tree clean), say so and stop.
Do not push — only commit locally unless the user explicitly asks to push.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 52 lines · 0 tokens per session scan A e461bb37ab42

Subscribe to this mod's changes

after-changes is a skill published in the GitHub repository Jessinra/Lorekeeper (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 85 tokens to every session and 559 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code Code review Commits Git and workflow agent-memory agentic-ai agentic-workflows ai-memory claude-code-memory

github-pr-workflow

Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.

paperclipai/paperclip · 39 tokens

pre-pr

Prepare a Honcho change for a pull request to plastic-labs/honcho. Invoke before opening a PR, when drafting a PR body, when asked if a branch is PR-ready, or when filling the pull request template. Checks required tests and docs, then writes Description / Proofs / Fixes.

plastic-labs/honcho · 65 tokens

merge-queue

Process the Refinery merge queue - collect agent work, detect and resolve conflicts, merge in dependency order, and verify integration.

a5c-ai/babysitter · 29 tokens

ase-repo-review

Perform a holistic, human-reviewer-style critique of the currently staged Git changes (or, with --unstaged, of the unstaged and untracked changes, with --branch, of a branch against its base, or, with --commit, of a single commit) and emit an approve/reject verdict with prioritized, severity-tagged, line-cited…

rse/ase · 111 tokens

commitlore-commits

Use when about to make a git commit and there is decision context worth recording — a constraint that shaped the change, an alternative that was tried and dropped, a warning for whoever touches this next. Drives the CommitLore capture pipeline, which drafts a record from the session transcript and the staged diff…

MongLong0214/commitlore · 235 tokens

commitlore-setup

Use when a git repository needs CommitLore wired up for the first time, or when its hook/notes configuration looks broken. Runs the diagnostic, installs the commit-msg validation hook, fixes the notes fetch refspec so records survive a clone or fetch, and builds the local record index. Trigger phrases include "set up…

MongLong0214/commitlore · 129 tokens

Lorekeeper: Skill for Claude Code