light-review-existing-diffs
Scannednpx machina-cli add skill gologo13/agent-skills/light-review-existing-diffs --openclawLight Review Existing Diffs
Overview
Perform a quick quality pass on current diffs to surface risky areas, ensure polish, and flag follow-up actions for deeper review.
Steps
- Scan recent changes
- List open branches or pending commits requiring review
- Skim side-by-side diffs focusing on new or modified files
- Note files or modules with large or complex edits
- Assess quality signals
- Watch for TODOs, debug code, or commented blocks needing cleanup
- Verify naming, formatting, and imports follow project standards
- Check that tests or documentation were updated when behavior changed
- Flag next actions
- Mark sections that warrant full review or pair programming
- Capture questions or uncertainties to raise with the author
- Document any quick fixes you can apply immediately
Review Checklist
- High-risk files identified
- Debugging artifacts removed or flagged
- Style and conventions validated
- Tests/docs updates confirmed or requested
- Follow-up items recorded for deeper review
Source
git clone https://github.com/gologo13/agent-skills/blob/main/skills/light-review-existing-diffs/SKILL.mdView on GitHub Overview
Light Review Existing Diffs performs a fast quality pass on current diffs to surface risky areas, ensure polish, and flag follow-up actions for deeper review. It helps catch issues early and aligns diffs with project standards. Use it only on explicit requests to avoid routine disruption.
How This Skill Works
Scan recent changes by listing open branches or pending commits and skim side-by-side diffs focusing on new or modified files. Assess quality signals by checking for TODOs, debug code, and formatting, as well as whether tests or documentation were updated when behavior changed. Finally, flag next actions by marking sections for full review, capturing questions, and documenting any quick fixes you can apply immediately.
When to Use It
- Before merging a feature branch to surface high-risk areas and polish diffs
- When a large refactor touches multiple modules and interfaces
- If diffs contain debugging artifacts or TODOs that require cleanup
- When behavior changes require confirmation that tests/docs were updated
- To prep for a quick pair programming session or follow-up review
Quick Start
- Step 1: Scan recent changes by listing branches or commits and skim diffs for new or modified files
- Step 2: Assess quality signals such as TODOs, debug code, formatting, imports, and updated tests/docs
- Step 3: Flag next actions by marking sections for full review, capturing questions, and noting quick fixes you can apply
Best Practices
- Prioritize high-risk files and modules first
- Flag all debugging artifacts and TODOs for cleanup
- Verify that naming, formatting, and imports follow standards
- Ensure tests and documentation reflect behavioral changes
- Capture clear follow-up actions and questions for the author
Example Use Cases
- Review a feature branch with multiple edits to surface hotspots
- Inspect a core API change to confirm tests/docs updated
- Identify and flag lingering debug code before review
- Document quick fixes you can apply immediately
- Gather questions for a pair programming session
