con un clic
review
Review code changes against project standards and conventions
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Menú
Review code changes against project standards and conventions
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Create git commit following project conventions
Full Jira-tracked change workflow — create/select Jira ticket under epic SDK-5256, create feat/SDK-XXXX branch, commit with ticket id, push, and open PR with ticket id in title and Jira links in body
Generate test JSON configurations following JSON_STRUCTURE_REFERENCE.md rules
Show current project status and development phase progress
Run tests for Android or iOS SDK
| name | review |
| description | Review code changes against project standards and conventions |
| user-invocable | true |
| disable-model-invocation | false |
Performs comprehensive code review of changes against Native Display System project standards, conventions, and best practices.
# Review all uncommitted changes
/review
# Review specific file
/review android/sdk/src/main/kotlin/models/Container.kt
# Review staged changes only
/review --staged
# Review specific commit
/review abc1234
Analyzes Changes
Validates Against Standards
Security Review
Generates Report
@Serializable for models!! operator (null assertion)Codable for models!Validates against .claude/reference/ documentation:
Ensures Android and iOS implementations are consistent:
Checks for common security issues:
Identifies performance concerns:
Ensures proper documentation:
📋 Code Review Report
=====================
Platform: Android
Files Changed: 5
Lines Added: +150
Lines Removed: -45
🔴 CRITICAL Issues: 0
🟠 HIGH Issues: 1
🟡 MEDIUM Issues: 3
🟢 LOW Issues: 2
---
🟠 HIGH: Missing input validation
Location: android/sdk/src/main/kotlin/evaluator/VariableEvaluator.kt:67
Issue: Variable path not validated before parsing
Fix: Add validation to check for empty or malformed paths
Impact: Could cause crashes with malformed input
🟡 MEDIUM: Inconsistent naming
Location: android/sdk/src/main/kotlin/models/Container.kt:23
Issue: Property named `child_arrangement` instead of `childArrangement`
Fix: Rename to follow camelCase convention
Impact: Inconsistent with project style
🟡 MEDIUM: Missing null check
Location: android/sdk/src/main/kotlin/resolver/StyleResolver.kt:45
Issue: Accessing parent.style without null check
Fix: Use safe call operator: parent?.style
Impact: Potential NPE if parent is null
🟡 MEDIUM: Large function
Location: android/sdk/src/main/kotlin/rendering/Renderer.kt:120
Issue: Function has 78 lines, should be split
Fix: Extract layout calculation and styling into separate functions
Impact: Reduces readability and maintainability
🟢 LOW: TODO comment
Location: android/sdk/src/main/kotlin/models/Background.kt:34
Issue: TODO comment for gradient implementation
Fix: Track as issue or implement now
Impact: Incomplete feature
🟢 LOW: Unused import
Location: android/sdk/src/main/kotlin/utils/ColorParser.kt:8
Issue: Import android.graphics.Color not used
Fix: Remove unused import
Impact: Code cleanliness
---
✅ GOOD PRACTICES:
- Proper use of @Serializable on all models
- Good test coverage for new features
- Clear function naming
- Proper error handling in parser
📊 CROSS-PLATFORM PARITY:
✅ Container implementation matches iOS
✅ Style resolution logic consistent
⚠️ iOS equivalent not yet implemented for gradient backgrounds
🔒 SECURITY:
✅ No security issues detected
✅ Input validation present
✅ No exposed secrets
---
OVERALL: 6 issues found (0 critical, 1 high, 3 medium, 2 low)
RECOMMENDATION: Fix HIGH issue before merging
# Make changes
# Stage changes
git add .
# Review before committing
/review --staged
# Fix issues
# Review again
/review --staged
# When clean, commit
/commit
# Complete feature
# Build and test
/build
/test
# Review all changes
/review
# Fix issues
# Review again
/review
# Create PR when clean
These issues automatically get CRITICAL severity:
These issues automatically get HIGH severity:
These issues automatically get MEDIUM severity:
These issues automatically get LOW severity:
If review flags something incorrectly:
// review-ignore: reason markerAdd project-specific rules to .claude/review-rules.md:
# Custom Review Rules
## Color Format
- All colors must be RGBA format
- Check: #RRGGBBAA or #RRGGBB
- Invalid: rgb(), rgba(), color names
## Layout Required
- All nodes must have layout property
- Check: node.layout is defined
- Invalid: missing layout object
Tracks over time:
/build - Build before review/test - Test before review/commit - Commit after review passesReview configuration in .claude/settings.json:
{
"review": {
"maxFunctionLines": 50,
"requireDocumentation": true,
"enforceNamingConventions": true,
"checkCrossPlatformParity": true,
"securityChecks": true
}
}
Files excluded from review (auto-generated, third-party):
*.generated.kt*.generated.swiftbuild/.build/node_modules/Pods/Review results saved to:
.claude/reviews/
├── 2024-01-15-feature-gallery.md
├── 2024-01-16-fix-styling.md
└── 2024-01-17-refactor-layout.md
Use review data to:
Reviews only changed lines, not entire files
Understands feature context from commit history
Identifies common anti-patterns from past reviews
Provides fix suggestions with code snippets