From cc-workflows
Performs thorough code reviews covering code quality, security, architecture, and UI/UX. Use when reviewing code changes, PRs, implementations, or when asked to review, audit, or assess code quality. Generates detailed reports with prioritized findings.
npx claudepluginhub tolo/coding-agent-toolkit --plugin cc-workflowsThis skill uses the workspace's default tool permissions.
Comprehensive code review covering quality, security, architecture, and UI/UX aspects.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Comprehensive code review covering quality, security, architecture, and UI/UX aspects.
checklists/ subdirectory for systematic assessmentgh pr diff <number> to get changesgit status --porcelain and git diff to identify changesgit log -10 --oneline to understand recent commitstree -d -L 3 and git ls-files | head -250 for codebase overviewGate: Scope determined, relevant files identified
Perform applicable reviews using the checklists.
Checklist: CODE-REVIEW-CHECKLIST.md
Assess:
Checklist: SECURITY-REVIEW-CHECKLIST.md
Assess:
Checklist: ARCHITECTURAL-REVIEW-CHECKLIST.md
Assess:
Checklist: UI-UX-REVIEW-CHECKLIST.md
Assess:
Gate: All applicable reviews complete
Categorize findings by priority:
Identify obsolete/temporary files and code requiring cleanup
Check for unmotivated complexity, over-engineering, or duplication
Verify adherence to project guidelines and patterns
Gate: Findings categorized and validated
Generate markdown report with:
# Review Report - [Date]
## Summary
[2-3 sentence overview of review scope and overall assessment]
## CRITICAL ISSUES
[Each issue: Title, Impact, Location, Fix Required]
## HIGH PRIORITY
[Each issue: Title, Impact, Location, Recommendation]
## SUGGESTIONS
[Brief list of improvements]
## Cleanup Required
- [Obsolete/temporary files to remove]
- [Dead code to remove]
## Compliance
- Guidelines adherence: [Assessment]
- Architecture patterns: [Assessment]
- Security best practices: [Assessment]
- [UI/UX if applicable]: [Assessment]
## Next Steps
1. [Prioritized action items]
Store report at: <project_root>/.agent_temp/reviews/<feature-name>-code-review-<YYYY-MM-DD>.md
Return report location to user.