version-control-review

version-control-review is a skill for Claude Code, Codex from soden46/engineer-flow. It costs 27 tokens per session (339 once invoked), scanned A, original, MIT.

A set of practices for inspecting code changes and managing version-control work such as commits, branches, merges, and reviews.

In plain words
What is it for?
Use it to review changes, prepare coherent commits, resolve merges, check branches, and verify work before it is integrated.
Why use it?
It helps catch regressions, security or data problems, test gaps, conflicts, and unrelated changes before merging.

Skill for Claude CodeCodex

Part of the engineer-flow plugin — 18 skills shipped together

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.

agentmods
npx agentmods add skills/soden46/engineer-flow/version-control-review
Any agent
npx skills add soden46/engineer-flow --skill version-control-review
Clone the repo
git clone --depth 1 https://github.com/soden46/engineer-flow

Made for: Claude Code, Codex.

Or install engineer-flow, the plugin that ships this one along with the rest of its 18 skills.

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 version-control-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/soden46/engineer-flow/version-control-review.svg)](https://agentmods.dev/skills/soden46/engineer-flow/version-control-review)
Your own site
<a href="https://agentmods.dev/skills/soden46/engineer-flow/version-control-review"><img src="https://agentmods.dev/badge/skills/soden46/engineer-flow/version-control-review.svg" alt="Measured on agentmods" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 339 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00027 $0.00339
Opus 5 $0.00014 $0.00169
Sonnet 5 $0.00005 $0.00068
Haiku 4.5 $0.00003 $0.00034

Measured 4d ago against content hash f0c604888612, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

version-control-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 4d 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.

skills/engineer-flow/core/version-control-review/SKILL.md · 65 lines

What it actually says

version-control-review

Use this skill for code review, change inspection, commits, merges, branch workflows, and review preparation.

Code Review

Evaluate:

  • correctness
  • regressions
  • security impact
  • data integrity
  • tests
  • maintainability
  • scope creep

Prioritize behavior-affecting problems over style preferences.

Review changed behavior in context, not only individual lines.

Changes

Keep commits coherent where practical.

Avoid mixing unrelated changes.

Before merging:

  • ensure conflicts are resolved intentionally
  • run relevant verification
  • inspect unexpected generated or configuration changes

Do not rewrite shared history without understanding the collaboration impact.

Adaptation

Use project evidence to determine the actual language, framework, runtime, and existing conventions.

When stack-specific implementation guidance is needed, prefer project evidence, native framework or language mechanisms, and relevant user-installed specialist skills. Technology-specific guidance must not redefine or weaken the core engineering requirement.

Absorbed Legacy Capability: code-review

The following framework-agnostic knowledge was preserved from the previous Engineer Flow capability during consolidation.

Code Review

Prioritize findings over summaries.

  • Look for bugs, regressions, security issues, and missing tests.
  • Ground findings in files, commands, or observable behavior.
  • Order issues by severity.
  • State residual risk when checks are incomplete.
  • Keep style-only comments secondary.
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. 4d ago First seen · 65 lines · 27 tokens per session scan A f0c604888612

Subscribe to this mod's changes

version-control-review is a skill published in the GitHub repository soden46/engineer-flow (3 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 339 once invoked, about $0.0001 per session on Opus 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 skills, from other repositories

todos

This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…

JetBrains/thinkrail · 127 tokens

writing-workflow-skills

Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.

JetBrains/thinkrail · 60 tokens

clarify

Adaptive requirements clarification with auto-depth routing. Shallow (Q&A) for simple tasks, Deep (exploration + DRAFT + PLAN) for complex ones. Escalates automatically when ambiguity persists.

mag123c/toktrack · 43 tokens

writing-specs

Use when a workflow step drafts or revises a spec artifact — a goal-and-requirements, an architecture, or a module SPEC — or when a workflow skill names it at such a step. The shared quality bar for specs — not a workflow, nothing to execute.

JetBrains/thinkrail · 59 tokens

detecting-process-injection-techniques

Detects and analyzes process injection techniques used by malware including classic DLL injection, process hollowing, APC injection, thread hijacking, and reflective loading. Uses memory forensics, API monitoring, and behavioral analysis to identify injection artifacts. Activates for requests involving process…

adriannoes/awesome-agentic-ai · 78 tokens

extracting-iocs-from-malware-samples

Extracts indicators of compromise (IOCs) from malware samples including file hashes, network indicators (IPs, domains, URLs), host artifacts (file paths, registry keys, mutexes), and behavioral patterns for threat intelligence sharing and detection rule creation. Activates for requests involving IOC extraction, threat…

adriannoes/awesome-agentic-ai · 82 tokens