How do I install the Review Changes skill?

Run npx skillmds@latest add timothywarner-org/review-changes in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Review Changes safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Review Changes?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Review Changes free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Review Changes?

timothywarner-org (@timothywarner-org) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Review Changes by timothywarner-org

Name: Review Changes
Rating: 4.2 (5 reviews)
Author: timothywarner-org

Review Changes

Review uncommitted local changes in the current git working tree for bugs, smells, missing tests, and CLAUDE.md voice violations. Use when the user asks to "review my changes", "look at my diff", "check my staged changes", "code review my working tree", or wants a sanity check before committing or opening a PR. Do NOT use for already-open pull requests on GitHub (that's the separate `review` command).

File contents

Review uncommitted changes

The current diff, status, and recent history are inlined below. Read them before responding.

Working tree diff

git diff HEAD

Index + working tree status

git status --short

Last 5 commits (for tone and style reference)

git log -5 --oneline

Your task

Review the changes above. Flag bugs, anti-patterns, missing tests, and any violation of this repo's voice rules. Be terse, be honest, no glazing.

Hard checks (block-on-find)

No em dashes. Hyphens with spaces, commas, or periods only.
Never use "ask" as a noun. "A heavy ask" is a rewrite.
No AWS references. Not in code, not in comments, not in docs.
No hardcoded secrets. Flag any string that looks like an API key, token, or password.
No console.log in shipped JS/TS. Test files and demos in segment_*/ are fine.

Soft checks (note, don't block)

Comments explain WHY, not WHAT. Code shows what; comments justify design.
PowerShell-first for shell scripts. Bash is the fallback.
Azure-first for cloud examples. Never compare to other clouds.
Docstrings/JSDoc on every new function or PowerShell script.
Idempotent re-runs where state mutation is involved.

Report format

## Blockers
- file:line - issue - proposed fix

## Soft findings
- file:line - note

## What's working
- one or two things the diff got right (keep it brief, no glazing)

If the diff is empty, say so and stop. Do not invent findings.

---name: review-changesdescription: Review uncommitted local changes in the current git working tree for bugs, smells, missing tests, and CLAUDE.md voice violations. Use when the user asks to "review my changes", "look at my diff", "check my staged changes", "code review my working tree", or wants a sanity check before committing or opening a PR. Do NOT use for already-open pull requests on GitHub (that's the separate `review` command).---# Review uncommitted changesThe current diff, status, and recent history are inlined below. Read them before responding.## Working tree diff```!git diff HEAD```## Index + working tree status```!git status --short```## Last 5 commits (for tone and style reference)```!git log -5 --oneline```## Your taskReview the changes above. Flag bugs, anti-patterns, missing tests, and any violation of this repo's voice rules. Be terse, be honest, no glazing.### Hard checks (block-on-find)1. **No em dashes**. Hyphens with spaces, commas, or periods only.2. **Never use "ask" as a noun**. "A heavy ask" is a rewrite.3. **No AWS references**. Not in code, not in comments, not in docs.4. **No hardcoded secrets**. Flag any string that looks like an API key, token, or password.5. **No `console.log` in shipped JS/TS**. Test files and demos in `segment_*/` are fine.### Soft checks (note, don't block)1. **Comments explain WHY, not WHAT**. Code shows what; comments justify design.2. **PowerShell-first for shell scripts**. Bash is the fallback.3. **Azure-first for cloud examples**. Never compare to other clouds.4. **Docstrings/JSDoc** on every new function or PowerShell script.5. **Idempotent re-runs** where state mutation is involved.### Report format```## Blockers- file:line - issue - proposed fix## Soft findings- file:line - note## What's working- one or two things the diff got right (keep it brief, no glazing)```If the diff is empty, say so and stop. Do not invent findings.

Frequently asked questions