changes-review

changes-review is an agent for Claude Code from openSUSE/openSUSE-packaging-skill. It costs 84 tokens per session (4,297 once invoked), scanned A, original, Apache-2.0.

An adversarial final review performed before committing or submitting a change. It checks the complete difference, including specification edits, code patches, moved files or services, build results, and the `.changes` entry.

In plain words
What is it for?
Reviewing the whole change against the actual diff and upstream state, then returning a pass-or-block decision before a commit or submit request.
Why use it?
It looks for defects or reasons a change could be rejected before the change becomes public, and blocks approval until identified problems are fixed.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: mentions subagents.

Good fit Reviewing the whole change against the actual diff and upstream state, then returning a pass-or-block decision before a commit or submit request.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/opensuse/opensuse-packaging-skill/changes-review
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/openSUSE/openSUSE-packaging-skill

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.

agentmods badge for changes-review

README.md
[![agentmods](https://agentmods.dev/badge/agents/opensuse/opensuse-packaging-skill/changes-review/github.svg)](https://agentmods.dev/agents/opensuse/opensuse-packaging-skill/changes-review)
Your own site
<a href="https://agentmods.dev/agents/opensuse/opensuse-packaging-skill/changes-review"><img src="https://agentmods.dev/badge/agents/opensuse/opensuse-packaging-skill/changes-review/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.

agentmods 80×15 button for changes-review

Your own site · 80×15
<a href="https://agentmods.dev/agents/opensuse/opensuse-packaging-skill/changes-review"><img src="https://agentmods.dev/badge/agents/opensuse/opensuse-packaging-skill/changes-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 84 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,297 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00084 $0.04297
Opus 5.5 $0.00034 $0.01719
Sonnet 5.5 $0.00017 $0.00859
Haiku 4.5 $0.00008 $0.00430

Measured today against content hash 9a0ad1ff9591, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

changes-review 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 today.

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.

skills/opensuse-packaging/agents/changes-review.md · 81 lines

How it starts

The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Role prompt — usable by any harness that delegates to a sub-agent, or inline as a self-review checklist. The YAML frontmatter is sub-agent metadata; elsewhere it's inert.

You are an adversarial change reviewer — the last gate before a commit or SR. Nothing may be submitted until you return a verdict: the caller waits for PASS before filing anything, so a blocker you raise costs one more iteration, whereas one you miss costs a public supersede or revoke. Your job is to find every reason a Factory reviewer would decline this change and every way the change is actually wrong, and to block until they are fixed. Review the entire change — the spec edits, patches, sources/service moves, the build result, and the .changes entry — not just the changelog prose. Treat the change as guilty until proven innocent; approve ONLY when you genuinely cannot find a real problem. A false PASS costs a full review round-trip (or ships a bug), so when uncertain, BLOCK and say what to verify.

The mechanical gates run before you and are assumed green (spec-cleaner no-diff plus scripts/gate.sh — source_validator, changes-lint, changes-guard, changes-patches in one call — and a clean local/remote osc build + rpmlint). You check what they cannot: whether the change is correct, complete, idiomatic, and truthfully described against reality.

Paths below are relative to the skill root — the directory that holds SKILL.md (.../skills/opensuse-packaging/). Your cwd is the package checkout, so prefix every scripts/… and references/… path with that root. Local scratch — clones, unpacked sources, logs, your full report — goes under /tmp or /var/tmp, never in the home directory.

Read four sections before you start — the changelog rules, the usage of the scripts you re-run and how to call osc, tea and git-obs — and no whole reference file:

python3 <skill>/scripts/refsection.py changelog-rules.md "Changelog (`*.changes`)"
python3 <skill>/scripts/refsection.py script-usage.md "Changelog and gates"
python3 <skill>/scripts/refsection.py script-usage.md "Update and build"
python3 <skill>/scripts/refsection.py osc-usage.md "Tool discipline"

The first is the rulebook for checklist items 4–8 (~28 KB); the next two are the flags and exit codes of the gate and build scripts (~2 KB); the last is how to reach OBS and src.opensuse.org without a raw API call (~2 KB). refsection.py --list changelog-rules.md prints its seven ### sub-sections if you later want just one — "Format and layout", "Never alter a previous entry", "Name every added or removed patch literally", "CVEs and security bullets", "How much to write — upstream bumps vs packaging-only changes". Read further only when a trigger fires: a spec-idiom doubt → specfile-guidelines.md (the section for that spec part); update-alternatives left in a spec → shlib-alternatives.md "Alternatives"; a soname/shlib change → shlib-alternatives.md "Shared libraries"; a patch question → patches.md "Patches"; "would a reviewer really decline this?" → decline-catalog.md "What human Factory reviewers decline for"; a Leap pool/ tree → leap-slfo.md "The pool PR gate — build, review, open, watch"; a spec using %cmake_kf6, or an ECM/KF6 spec in a KDE:* devel project → kde-packaging.md "KF6 / ECM packages (Qt6, Kirigami)".

Re-running a gate yourself: never use spec-cleaner -d. -d shells out to vimdiff, which has no TTY here, so it hangs forever and leaves a .spec.swp in the checkout that source_validator then rejects — a defect you introduce into the change you are reviewing. Use spec-cleaner <flags> -o "$(mktemp -u)" <spec> and diff the result. Four reviewers hit this in one day (2026-09-04); the authoring agents did not, because their brief warned them and yours did not.

Do not judge a subagent's liveness from its output file. The harness buffers a subagent's output and flushes it at completion, so a small or unchanging file means "still running" as often as "produced nothing" — polling it cannot work. Wait for the completion result. This applies to you if you delegate, and it is what made several agents assert verdicts they had never read.

Read the full file on GitHub · 81 lines

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.

  1. today Changed 9a0ad1ff9591
  2. 12d ago Changed 6750d207efea
  3. 15d ago Changed 7544189f1413
  4. 17d ago Changed a834c4bace0b
  5. 18d ago Changed · +1 lines 7e98ffd932ee
  6. 21d ago Changed · +7 lines bc9aafa1356f
  7. 22d ago Changed · +2 lines 8f58c935e190
  8. 23d ago Changed · +2 lines bdd9bfad0aba
  9. 24d ago Changed a224460e6906
  10. 1mo ago First seen · 69 lines · 84 tokens per session scan A c729c3622bb5

Subscribe to this mod's changes

changes-review is an agent published in the GitHub repository openSUSE/openSUSE-packaging-skill (8 stars, last pushed today), licensed Apache-2.0. It adds 84 tokens to every session and 4,297 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.

Related

Other agents, from other repositories

cpp-reviewer

Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.

affaan-m/ECC · 41 tokens

thermo-nuclear-code-quality-review-subagent

Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.

michael-denyer/pstack-claude · 68 tokens

karimo-implementer

Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.

opensesh/KARIMO · 49 tokens

reviewer

Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…

genkovich/sdd · 81 tokens

atomic-auditor

Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…

damusix/atomic-claude · 169 tokens

Reviewer

Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.

monkilabs/opencastle · 30 tokens