- Home
- /
- Categories
- /
- Code Review
Code Review
Automated code review and analysis
dart-resume
by dartsim
"DART Resume: continue work from a previous session"
dart-retro
by dartsim
"DART Retro: run a retrospective and capture durable lessons"
dart-build
by dartsim
"DART Build: CMake, pixi, dependencies, and build troubleshooting"
dart-fix-ci
by dartsim
"DART Fix CI: debug and fix failing CI checks on any base branch"
dart-next
by dartsim
"DART Next: select and execute the next bounded DART task"
dart-branch-cleanup
by dartsim
"DART Branch Cleanup: analyze or clean stale repository branches"
dart-execute-packet
by dartsim
"DART Execute Packet: select and execute one orchestrator-authored work packet from a numbered plan"
dart-verify-sim
by dartsim
"DART Verify Sim: text-first and visual checks for 3D scenes and physics (metrics, scene dump, trajectories, headless render, image verdict/golden)"
dart-changelog
by dartsim
"DART Changelog: decide, draft, finalize, or audit DART changelog entries"
dart-ultrawork
by dartsim
"DART Ultrawork: kick off a large or autonomous DART task with project-home docs, an optional decision interview, and orchestrated execution"
dart-deps
by dartsim
"DART Deps: triage and shepherd dependency and bot pull requests"
dart-pr
by dartsim
"DART PR: create a branch, commit, push, and open a DART pull request"
dart-ci
by dartsim
"DART CI: GitHub Actions, cache debugging, and platform-specific failures"
receiving-code-review
by srbhr
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
code-review
by srbhr
Review code for correctness, security, performance, and Resume Matcher conventions. Use when receiving code review feedback or before submitting PRs. Requires technical rigor, not performative agreement.
receiving-code-review
by srbhr
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
nextjs15-performance
by srbhr
Next.js 15 critical performance fixes. Use when writing React components, data fetching, Server Actions, or optimizing bundle size.
nextjs-performance
by srbhr
Next.js critical performance fixes. Prevents async waterfalls, reduces bundle size, secures Server Actions, and ensures correct production builds. Use when writing React components, data fetching, Server Actions, or optimizing bundle size.
ui-review
by srbhr
Review UI changes against Swiss International Style design system. Checks colors, typography, borders, shadows, spacing, and anti-patterns. Use before committing any frontend UI changes.
ui-review
by srbhr
Review UI changes against Swiss International Style design system. Checks colors, typography, borders, shadows, spacing, and anti-patterns. Use before committing any frontend UI changes.
update-docs
by ryokun6
Update ryOS documentation by analyzing the codebase and syncing docs with current implementation. Use when updating docs, syncing documentation, or when docs are outdated.
audit-permissions
by malob
This skill should be used when the user asks to "audit claude permissions", "audit permissions", "review local claude settings", "promote permissions to global", "clean up claude settings", "find permission patterns", or wants to identify project-local Claude Code permissions that should be added to global configuration.
budget-optimizer
by OneWave-AI
Analyze spending patterns and find savings. 50/30/20 rule, subscription audit, debt payoff strategies, emergency fund roadmap.
verify-translator
by zotero
Steps that MUST be performed to verify a Zotero translator after every addition or modification, and before submitting a PR.