Menu

Individual skill

reviewing-code-changes

0upvotes

Perform a security review of a diff, branch, or pull request — assessing what the change introduces, weakens, or exposes, with a triage-first workflow and false-positive discipline. Use when asked to security review a PR or branch, check a diff before merge or commit, or assess whether a change is safe to ship.

secskills-core/skills/reviewing-code-changes/SKILL.md

Read pinned source

Source commit ca53957bcd8e3b83b5d4d190bb3ad008a4f15c84

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
188
Repository last updated
Sep 4, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Reviewing Code Changes

Reviewing a diff is not auditing a codebase in miniature. The diff shows you
what changed but hides what the change *means* — the caller that now receives
untrusted data, the check that used to run, the assumption that no longer
holds. Reviewing only the added lines is the standard way to miss the bug.

## When to Use

- Security review of a pull request, branch, or commit range
- Pre-commit or pre-merge check on your own changes
- Assessing risk of a dependency bump or config change
- Reviewing an AI-generated change before it ships
Back to top