Review Uncommitted Changes

VerifiedSafe

Reviews uncommitted working changes using 'git diffall' to identify logic errors, unwanted behavior, and bugs. Does not summarize changes but focuses on actual or potential issues, including significant omissions.

Sby Skills Guide Bot
DevelopmentIntermediate
206/2/2026
Claude CodeCursorWindsurf
#code-review#git#uncommitted-changes#bug-detection

Recommended for

Our review

Reviews uncommitted working changes in a Git repository to identify logic errors, bugs, and unwanted behavior.

Strengths

  • Quick detection of issues in modified code without unnecessary summarization
  • Leverages git diffall for a comprehensive view of all changes
  • Focuses on bugs and logic errors rather than style or formatting

Limitations

  • Does not provide a summary or high-level overview of changes
  • Limited to uncommitted changes only
  • Depends on the quality of the diff and may miss broader context issues
When to use it

Use this skill right after making local changes to verify they are bug-free before committing.

When not to use it

Do not use it for a full code review involving remote files or when you need a summary of changes.

Security analysis

Safe
Quality score85/100

The skill only executes 'git diffall', a read-only command that displays uncommitted changes. It does not modify files, exfiltrate data, or invoke any destructive operations. The allowed-tools list explicitly restricts Bash to this single command, preventing misuse.

No concerns found

Examples

Review latest uncommitted changes for bugs
Review my uncommitted changes for any logic errors or bugs.
Find unwanted behavior in working tree
Look at the uncommitted diff and point out any potential unwanted behavior or missing edge cases.

name: review-uncommitted description: Review the working changes that are uncommitted for issues allowed-tools: Bash(git diffall) disable-model-invocation: true

Review the working changes that are uncommitted for issues. You should retrieve these working changes by running git diffall. Don't summarize the changes. You should focus on errors in logic, unwanted behavior and bugs. If you feel strongly that the changes are missing something that wouldn't necessarily qualify as a bug, feel free to point them out as well.

Related skills