Browse Secure Claude Skills
Search verified agent skills and review security grades before installing · full A–Z index
- Code ReviewerFind bugs, security holes, and maintainability issues in a diff or file.Votes: 0GitHub stars: 168
- Code ReviewStandalone code review methodology for structured, severity-classified code assessmentVotes: 0GitHub stars: 460
- Code ReviewReview changes for real correctness, maintainability, regressions, missing tests, and integration defects with low-noise findings.Votes: 0GitHub stars: 2
- Code ReviewerReviews code for security vulnerabilities, performance issues, and best practices. Use when reviewing code, performing security audits, checking for code quality, reviewing pull requests.Votes: 0GitHub stars: 416
- Code ReviewReview code changes for correctness, maintainability, and operational risk.Votes: 0GitHub stars: 2
- Code ReviewReviews a diff for defects. Use when the user asks to review a pull request or inspect changes.Votes: 0GitHub stars: 2
- Code ReviewReview the diff, do NOT modify code: 1. Matches approved plan? 2. Unrelated files touched? 3. Duplication? Error handling? Edge cases? 4. Style consistent? 5. Silent API/schema changes? Report by severity, then recommended fixes.Votes: 0GitHub stars: 2
- Code ReviewPerform thorough code reviews focusing on unused code, duplications, coding patterns, bugs, and optimizations. Use when user wants code reviewed or audited. Read-only - outputs findings without making changes.Votes: 0GitHub stars: 37
- Review CodeReview code for quality, correctness, and fit. Use when the user wants judgment on code that already exists — their own changes, a teammate's patch, a PR, branch, commit, diff, staged changes, or one or more files to look over. Activate on requests like review, look over, sanity check, critique, code review, or 'is this good?' The key signal is that the user wants evaluation of existing code and its tradeoffs, not implementation, debugging, or explanation. This skill works independently, but ...Votes: 0GitHub stars: 119
- Code ReviewComprehensive code review with security, performance, and best practices focusVotes: 0GitHub stars: 3
- Code ReviewPerform thorough code reviews, identify bugs, suggest improvements, and explain code quality issues. Use when the user shares code and asks for a review, bug hunt, or quality feedback.Votes: 0GitHub stars: 21
- ReviewReview code changes for correctness, security, and missing tests. Be specific about file:line.Votes: 0GitHub stars: 3
- Code ReviewConducts and responds to code review — reviewing a change for correctness, design, and risk, and evaluating review feedback received on your own work. Use this before merging, when asked to review a diff or pull request, when review feedback has arrived and needs acting on, or when feedback seems wrong and needs a reasoned response rather than compliance.Votes: 0GitHub stars: 1,651
- Code ReviewReview uncommitted changes or a specific diff — when asked to "check my code", "review this", "what is wrong with these changes". Not for writing new code.Votes: 0GitHub stars: 2
- Code ReviewingReview code for quality, security, and best practices. Use when the user asks for code review, wants feedback on their code, mentions reviewing changes, or asks about code quality.Votes: 0GitHub stars: 1,091
- Caveman Review超高压缩的 code review 留言。砍掉 PR 回馈的噪音，保留可运行的信号。 每则留言只有一行：位置、问题、修法。当用户说 "review this PR"、"code review"、 "review the diff"、"/review"，或调用 /caveman-review 时使用。 审查 pull request 时会自动触发。Votes: 0GitHub stars: 2
- Code ReviewReviews code changes for clarity and bugsVotes: 0GitHub stars: 8
- Code ReviewReview a git diff or branch for correctness bugs, risky changes and missing tests. Use when asked to review code, a branch or a pull request.Votes: 0GitHub stars: 2
- Code Review Best PracticesUse when conducting code reviews.Votes: 0GitHub stars: 2
- Code ReviewPerform thorough code reviews, identify bugs, suggest improvements, and explain code quality issuesVotes: 0GitHub stars: 21