Browse Secure Claude Skills
Search verified agent skills and review security grades before installing · full A–Z index
- Code Review JossteiStandalone code review methodology for structured, severity-classified code assessmentVotes: 0GitHub stars: 3
- Code Reviewer 13Performs critical code reviews with a skeptical mindset, assuming the author cannot be fully trusted. Evaluates code quality, architecture, testing, requirements, and production readiness. Use after completing significant code changes or before merging.Votes: 0GitHub stars: 2
- Code ReviewUse for an explicit review of a defined diff, pull request, file, or code scope for actionable defects and regressions. Does not authorize an unsolicited rewrite or replace native delegated review routing.Votes: 0GitHub stars: 2
- Common Code ReviewStandards for high-quality, persona-driven code reviews. Use when reviewing PRs, critiquing code quality, or analyzing changes for team feedback. (triggers: review, pr, critique, analyze code)Votes: 0GitHub stars: 43
- Code ReviewReview code changes for correctness, security, and maintainability with severity-ranked, evidence-based findings. Use when asked to review a diff, a pull request, or a file before merge.Votes: 0GitHub stars: 7
- Code ReviewProvides thorough code review with actionable feedbackVotes: 0GitHub stars: 76
- Code Review 90Guide for making code reviews. Use this when asked to make code reviews, or ask to use it before committing changes.Votes: 0GitHub stars: 2
- Code ReviewUse when a major project step has been completed and needs review against the plan and coding standards. Also use when someone says 'review this', 'check my code', 'is this ready', or when a significant chunk of implementation is done. Use after completing tasks from an implementation plan, before creating PRs, or when asked to assess code quality.Votes: 0GitHub stars: 15
- Code Review 77**MANDATORY**: Apply when reviewing code changes, PR diffs, or code-review requests. Enforces quality standards, warning seriousness, and meaningful comments.Votes: 0GitHub stars: 2
- Code Review 88Reviews code changes for bugs, style issues, performance problems, and best practices. Use when reviewing PRs, checking code quality, or auditing existing code.Votes: 0GitHub stars: 2
- Code ReviewStandalone code review methodology for structured, severity-classified code assessmentVotes: 0GitHub stars: 460
- Code Review 20Code review assistance with linting, style checking, and best practicesVotes: 0GitHub stars: 2
- Code Review PreferencesUse when reviewing code, PRs, or discussing code quality standards. Applies team coding standards and review methodology.Votes: 0GitHub stars: 416
- Code ReviewStructured pull-request and diff review: security, correctness, style, tests, and actionable feedback.Votes: 0GitHub stars: 22
- Code ReviewReviews code for quality, best practices, and potential issues. Use when asked to review, audit, or check code for problems.Votes: 0GitHub stars: 71
- Code Review 49Perform comprehensive code review with best practices analysis. Use when user asks for code review, code quality check, or wants to analyze their code for issues.Votes: 0GitHub stars: 2
- Code Review 112Review code changes for correctness, security, tests, and architecture; use for code review or PR review requests (trigger keywords: code review, review changes, PR review, security review).Votes: 0GitHub stars: 2
- Code Review 67Perform a thorough code reviewVotes: 0GitHub stars: 2
- Safe Code Review 12Safe implementation of code-review operations.Votes: 0GitHub stars: 15
- Clean Code Principles当编写新代码、评审 PR 或重构遗留代码时使用；依据 Uncle Bob《整洁代码》原则识别坏味道并把"能跑的代码"重写为"整洁的代码"，产出命名/函数/注释/错误处理等改进与检查清单；不适用于性能调优、架构选型或语言特性教学；触发词：整洁代码、重构、代码坏味道Votes: 0GitHub stars: 3