Find the best CLAUDE.md, AGENTS.md and Claude skills

Happy-Technologies-LLCSkill

code-review

Happy-Technologies-LLC/happy-platform-skills/skills/development/code-review/SKILL.md

Review ServiceNow code for security vulnerabilities, performance issues, and platform best practices

Often used withadd-new-model

anthroosSkill

code-review

anthroos/claude-code-review-skill/SKILL.md

AI code review for PR or local changes. 280+ checks across security, architecture, performance, testing, and code quality. Posts findings as GitHub PR comments with confidence scores.

Often used withadd-new-model

cenconq25Skill

code-review

cenconq25/claude-code-app-studio/.claude/skills/code-review/SKILL.md

Architectural and quality review of one or more files. Verifies coding standards, SOLID, testability, mobile anti-patterns, and ADR compliance. Use after /dev-story and before /story-done.

Often used withadd-new-model

Adrian333DevSkill

review-code

Adrian333Dev/flow/skills/work/review-code/SKILL.md

Reviews this session's code against the criteria in review-code.md.

padmarajnidagundiReads credentialsSkill

code-review

padmarajnidagundi/Playwright-AI-Agent-POM-MCP-Server/.github/skills/code-review/SKILL.md

Reviews Playwright test code for POM compliance, best practices, security, and coverage completeness. Auto-loaded when the user asks to review, audit, or inspect test files.

Often used withadd-new-model

flc1125Skill

code-review

flc1125/skills/skills/code-review/SKILL.md

Request or perform a git-backed code review for a defined diff or SHA range using implementation context and requirements. Use when finishing a task, completing a major feature, preparing to merge, or when you need a fresh review before proceeding.

Often used withadd-new-model

scottdurowSkill

code-review

scottdurow/power-platform-full-stack-skills/skills/code-review/SKILL.md

Deep code audit and technical review skill. Handles code audits (dead wiring, silent failures, stubs, bloat), architecture decisions, security audits, feature design reviews, refactoring plans, and deployment strategy reviews. Produces actionable reports with file:line references grouped by severity, or structured decision documents with trade-off analysis. Triggers on "code review", "audit the code", "review the code", "find dead code", "find placeholders", "check for stubs", "prune the code", "code cleanup", "implementation review", "completeness check", "find unused code", "architecture decision", "security audit", "design review", "refactoring plan", "deployment review", "team review", "review team", "collaborative review".

Often used withadd-new-model

fagemxSkill

code-review

fagemx/edda/.claude/skills/code-review/SKILL.md

Review merged code, commit ranges, or codebase paths for correctness, security, architecture, and test risk; use pr-review for open PRs

Often used withadd-new-model

muyenSkill

code-review

muyen/vibe-to-prod/.claude/skills/code-review/SKILL.md

Proactive code quality review. Triggers on significant code changes to check security, performance, architecture, and project patterns.

Often used withadd-new-model

nimadorostkarSkill

code-review

nimadorostkar/Claude-Skills-collection/skills/development/code-review/SKILL.md

Use when reviewing a pull request, diff, or branch. Produces severity-ranked findings covering correctness, security, performance, and maintainability, with concrete fixes rather than opinions. Trigger on "review this pr", "look over my diff before i push", "is this branch ready to merge", "anything wrong with this change". Do not use for a vulnerability-focused audit — see the security-review skill; for feature release readiness, see the qa-review skill.

Often used withadd-new-model

ptsilivisSkill

code-review

ptsilivis/autonomousguy/skills/code-quality/code-review/SKILL.md

Senior embedded-engineer code review. Defaults to Classic AUTOSAR embedded C and covers two concerns: (1) Correctness review — integer overflow, volatile correctness, ISR/task race conditions, stack usage, dynamic memory, control flow, AUTOSAR/ISO 26262 readiness, with findings rated Critical/Major/Minor; (2) Naming review — AUTOSAR Classic conventions for modules, SWC types, port names, runnables, C identifiers, typedefs, macros, and enumerations, aligned with MISRA Rule 5.x identifier uniqueness. Audits existing code and generates correctly-named identifiers for new work. Handles Adaptive AUTOSAR C++14+ when the input is C++ or names ara::, reviewing RAII, exceptions vs ara::core::Result, smart pointers, and AUTOSAR C++14 / MISRA C++:2023 naming. A third focus, legacy modernization assessment, proposes the smallest safe steps toward a MISRA-conformant, MCAL-abstracted, unit-tested state. Returns decision-ready findings with a built-in self-check and can emit a self-contained HTML report under analysis/.

Often used withadd-new-model

larchankaSkill

code-review

larchanka/skills/code-review/SKILL.md

Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.

Often used withadd-new-model

felipereisdevSkill

code-review

felipereisdev/code-review-skill/SKILL.md

Performs a structured, comprehensive code review of git changes (uncommitted, staged, current branch vs base, a single commit, a commit range, or a GitHub pull request or GitLab merge request by number or URL). Detects the stack and architecture automatically, applies stack- and pattern-specific rules, and reports findings by severity. Use when the user runs /code-review or /review-pr, or asks to "review my changes", "review PR", "review this branch", "do a code review", "revisar minhas mudanças", "revisar o PR" or "fazer code review".

Often used withadd-new-model

gsarigReads credentialsSkill

code-review

gsarig/skills/skills/code-review/SKILL.md

Orchestrator. Triages a PR, local diff, patch file, or staged/branch changes into one of four review types (content, code-lite, code-deep, infra) and dispatches to the matching child skill. Use this when you don't already know which depth or type of review you want. For a known type, invoke the child skill directly.

Often used withadd-new-model

galandoSkill

code-review

galando/piv-speckit/.claude/skills/code-review/SKILL.md

Auto-activates during code reviews

Often used withadd-new-model

lezli01Skill

code-review

lezli01/vincent/.claude/skills/code-review/SKILL.md

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

Often used withadd-new-model

megamottSkill

code-review

megamott/vibe-skills/skills/code-review/SKILL.md

Код-ревью изменений на качество, безопасность и соответствие стилю проекта

Often used withadd-new-model

with-logicSkill

code-review

with-logic/crew-skills/code-review/SKILL.md

Perform thorough code reviews of git changes (staged and committed) against a base branch, applying repo-specific review guidelines (.github/pr-review-prompt.md, CLAUDE.md) and general best practices. Use when asked to review a PR, diff, or set of changes and provide categorized feedback with file/line references and suggested fixes.

Often used withadd-new-model

Microsoft AzureSkill

code-review

Azure/typespec-azure/.github/skills/code-review/SKILL.md

Review diffs and pull requests in Azure/typespec-azure for compatibility, .chronus change descriptions, TypeSpec diagnostics and rulesets, SDK emitter and Spector contract regressions, and meaningful tests. Use for Copilot code review in this repository.

Often used withadd-new-model

mzbacSkill

code-review

mzbac/skills/skills/code-review-low/SKILL.md

Lightweight code review for diffs/PRs focusing on high-signal simplifications, code smells, security, performance, and whether new tests are needed; focus on recently modified code unless instructed otherwise.

Often used withadd-new-model