Full review
全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能,提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard
npx -y skills add bg-szy/TOP-SKILLS --skill full-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Comprehensive code review using all available skills. Use before committing or when you want a thorough analysis of changes. Triggers on review code, check changes, full review, pre-commit review.
SKILL.md
4.8 KB, as published. Nobody here has run it
Full Code Review
Orchestrates all available review skills to provide comprehensive code analysis.
When to Use
- Before committing code changes
- Performing pre-merge reviews
- Running comprehensive audits
- Checking code against all quality standards
- Validating changes across the full stack
Workflow
Step 1: Identify Changes
Get list of changed files using git diff.
Step 2: Map Skills to Files
Invoke relevant skills based on file patterns.
Step 3: Run Checklists
Apply security, DeFi, type safety, and performance checks.
Step 4: Generate Report
Produce structured report with severity levels.
Step 5: Auto-Fix (Optional)
Offer to fix critical issues automatically.
Trigger Phrases
- "review code", "check changes", "full review"
- "pre-commit review", "review before commit"
- "run all skills", "comprehensive review"
Review Process
Step 1: Identify Changes
# Get changed files
git diff --name-only HEAD~1 2>/dev/null || git diff --name-only
git status --porcelain
Step 2: Skill Mapping
Based on changed files, invoke these skills:
| Changed Files | Skills to Invoke |
|---|---|
Any .ts, .tsx | code-review-expert, common-pitfalls |
server/src/routes/* | system-integration-validator |
server/src/services/* | defi-expert, hft-quant-expert |
server/src/db/* | code-consistency-validator |
client/src/pages/*, client/src/components/* | apple-ui-design, common-pitfalls |
client/src/hooks/* | common-pitfalls (TanStack Query) |
rust-core/**/*.rs | code-consistency-validator, latency-tracker |
*token*, *protocol*, *chain* | defi-registry-manager |
*arbitrage*, *trade*, *swap* | liquidity-depth-analyzer |
*logger*, *error* | error-logger |
*websocket*, *ws* | common-pitfalls (WebSocket) |
schema.ts, *.sql | common-pitfalls (Drizzle) |
Step 3: Review Checklist
For EVERY review, check these critical items:
Security
- No SQL injection vulnerabilities
- No XSS in React components (dangerouslySetInnerHTML)
- No command injection in Bash calls
- No hardcoded secrets/credentials
- Proper input validation on all endpoints
- Rate limiting on sensitive routes
DeFi-Specific
- Token decimals correct (USDC/USDT=6, WBTC=8, ETH=18)
- Token addresses in checksum format
- BigInt handling (no precision loss with Number())
- Slippage protection on swaps
- Proper error handling for reverts
Type Safety
- No
as anytype assertions - Types match across TypeScript ↔ Rust ↔ PostgreSQL
- Zod schemas for all API inputs
- Proper null/undefined handling
Performance
- No N+1 queries
- Proper indexing on queried columns
- Timeouts on external calls
- Connection pooling configured
Code Quality
- Error messages don't leak internal details
- Consistent naming conventions
- No dead code or unused imports
- Proper async/await usage
TanStack Query (if applicable)
- QueryKeys use full URL paths
- Mutations invalidate relevant queries
- Using isPending (not isLoading) for mutations in v5
- Responses typed with schema types
Drizzle ORM (if applicable)
- No primary key type changes
- Array columns use
text().array()syntax - Insert/select types exported for models
- Using drizzle-zod for validation
React Components (if applicable)
- Loading/error states handled
- data-testid on interactive elements
- Using router Link, not window.location
- Helper functions defined before use
Blockchain/RPC (if applicable)
- All contract calls wrapped in try/catch
- Multicall uses
allowFailure: true - Prices validated against expected ranges
- Handling "execution reverted" gracefully
Step 4: Report Format
## Code Review Report
### Files Reviewed
- [list files]
### Skills Applied
- [list skills invoked]
### Critical Issues (MUST FIX)
🔴 [issue description]
File: path/to/file.ts:line
Fix: [how to fix]
### Warnings (SHOULD FIX)
🟡 [issue description]
File: path/to/file.ts:line
Suggestion: [recommendation]
### Suggestions (NICE TO HAVE)
🟢 [improvement idea]
### Summary
- Critical: X issues
- Warnings: X issues
- Suggestions: X items
- Ready to commit: Yes/No
Step 5: Auto-Fix
If critical issues found, offer to fix them:
- Show the issue
- Show the proposed fix
- Apply if approved
- Re-run validation
Quick Commands
/review- Full review of all changes/quick-review- Fast check of critical issues only- Invoke
full-reviewskill for this comprehensive process