# Version Control Review

> Review changes and manage commits, branches, merges, and code-review workflows using VCS-agnostic engineering principles.

- Skill: `soden46/version-control-review` (Agent Skill)
- Install (CLI): `npx skillmds@latest add soden46/version-control-review`
- Raw SKILL.md: https://api.skillmd.com/api/skills/soden46/version-control-review/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: soden46 (https://skillmd.com/u/soden46)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/soden46/version-control-review

---


# 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.

<!-- ENGINEER_FLOW_ABSORBED_CODE_REVIEW_START -->

## 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.

<!-- ENGINEER_FLOW_ABSORBED_CODE_REVIEW_END -->