review-changes
Scannednpx machina-cli add skill anilcancakir/claude-code-plugins/review-changes --openclawCode Review Task
Review all uncommitted changes in this repository for issues.
Steps
- Run
git diffto get all uncommitted changes - Run
git diff --cachedfor staged changes - For each modified file, analyze for:
- Security vulnerabilities (see references/security-checklist.md)
- Bugs and logic errors
- Code quality issues (see references/quality-checklist.md)
- Check test coverage for changed code
- Categorize findings as Critical/Warning/Suggestion
- Provide specific file:line references
- Suggest fixes with code examples
Reference Documents
For detailed checklists, read:
references/security-checklist.md- OWASP Top 10 and stack-specific securityreferences/quality-checklist.md- Code quality and best practices
Stack Detection
Detect project stack from config files:
composer.json+artisan= Laravelpubspec.yaml= Flutternuxt.config.*= Nuxt.jspackage.jsonwith "vue" = Vue
Apply stack-specific checks based on detection.
Output Requirements
Return a structured report with:
- Summary counts by severity
- Each issue with file:line, explanation, and fix
- Test coverage status
- Prioritized recommendations
Focus on actionable feedback. Skip style-only issues unless they affect readability significantly.
Source
git clone https://github.com/anilcancakir/claude-code-plugins/blob/main/pre-commit-flow/skills/review-changes/SKILL.mdView on GitHub Overview
This skill analyzes all uncommitted changes using git diff, checks for security vulnerabilities and quality issues, and flags bugs before committing. It uses stack-aware checks (Laravel, Vue/Nuxt.js, Flutter) and references dedicated checklists to guide fixes, including test coverage status.
How This Skill Works
It captures changes with git diff and git diff --cached, then analyzes each modified file against security (references/security-checklist.md) and quality (references/quality-checklist.md) checklists. Findings are categorized as Critical/Warning/Suggestion, reported with file:line references, and accompanied by concrete fixes and code examples. Stack detection tailors checks to Laravel, Flutter, Nuxt.js, or Vue projects.
When to Use It
- Before committing changes to a shared branch to ensure issues are caught early
- During code review or when asked to review a pull request
- After a major refactor that touches multiple files
- For security-sensitive changes (auth, input handling, dependencies)
- When adding new configurations or dependencies that affect behavior or security
Quick Start
- Step 1: Run git diff to capture all uncommitted changes
- Step 2: Run git diff --cached to capture staged changes
- Step 3: For each changed file, run security and quality checks, categorize issues, and propose concrete fixes with file:line references
Best Practices
- Always run git diff and git diff --cached to capture all changes
- Run stack-specific security and quality checklists before finalizing
- Verify test coverage for changed code and augment tests as needed
- Provide actionable fixes with precise file:line references
- Prioritize findings by Critical/Warning/Suggestion and address in order
Example Use Cases
- app/Http/Controllers/Auth/LoginController.php:88 - sanitize inputs and enforce CSRF tokens to prevent CSRF and injection vulnerabilities
- resources/js/components/SignupForm.vue:45 - escape user-visible output and validate email on client-side to reduce XSS risk
- lib/main.dart:120 - add null-safety guards and input validation for login flow
- nuxt.config.js:78 - enable CSP and set secure headers to mitigate clickjacking and XSS
- tests/unit/api.test.js:22 - ensure test coverage for error paths and edge cases
