Skills real projects publish on GitHub, most starred first. Each one says what it will make an agent do before you copy it.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
henriquecanerSkillhenriquecaner/brain-agent/.agents/skills/code-review/SKILL.md
Perform thorough code reviews. Use when reviewing PRs, auditing code quality, or checking for bugs and anti-patterns.
Often used withclose-specadd-new-modelcompare-screenshots
L-X-TSkillL-X-T/ng-agentic-skills/.agents/skills/code-review/SKILL.md
Code review changed, staged, last-commit, and merge or PR work against requirements and the repository style guide. Use when reviewing current work, staged changes, the last commit, a branch, a merge, or a pull request. For a whole-codebase style audit use ng-review-style-guide instead.
Often used withclose-specadd-new-modelcompare-screenshots
saeedvazirySkillsaeedvaziry/skills/skills/code-review/SKILL.md
Exhaustively review every line in a diff from a fixed point along two independent axes—repository standards and the originating spec—with evidenced findings, explicit coverage, and bounded fix verification.
Often used withclose-specadd-new-modelcompare-screenshots
MicrosoftSkillmicrosoft/amplifier-bundle-skills/skills/code-review/SKILL.md
Review changed code for reuse, quality, and efficiency, then fix any issues found.
Often used withclose-specadd-new-modelcompare-screenshots
Antune-LSkillAntune-L/skillzer/skills/code-review/SKILL.md
Review changed code (session, current branch, or colleague's branch) for principle violations, reinvented wheels, and dead code. Trigger after coding, before merge, or for PR review.
Often used withclose-specadd-new-modelcompare-screenshots
aws-solutionsSkillaws-solutions/konductor/skills/code-review/SKILL.md
Use when creating or submitting a pull request, reviewing a diff or PR from another developer, addressing PR feedback, or running a post-implementation review cycle on local changes. Uses standard git and GitHub CLI (`gh`) commands and classifies findings by severity (CRITICAL/IMPORTANT/SUGGESTION).
Often used withclose-specadd-new-modelcompare-screenshots
axiomanticSkillaxiomantic/spellbook/skills/code-review/SKILL.md
Use when the user EXPLICITLY asks for a lightweight pass, or for feedback/audit modes. Triggers: 'quick review', 'light review', 'look over this', '--quick', 'check my work', 'self-review before PR', 'review my code', 'audit this code', 'PR comments to address', 'reviewer said', 'address feedback', 'review PR #X comments'. NOT for: unspecified-scope branch review such as 'review this branch' or 'code review' (that DEFAULTS to advanced-code-review), or PR triage and summarization (use distilling-prs). This skill is the explicit opt-in to a lighter pass; if the user did not ask for lightweight by name, do not use it. Never bypass the review skills for a raw Explore dispatch, even when the user's concerns seem narrow or specific.
Often used withclose-specadd-new-modelcompare-screenshots
nledfordSkillnledford/engineering-review-board/skills/code-review/SKILL.md
Perform repository-local code reviews. Use for requested diff or pull-request audits, final focused review after implementation, or changes that affect behavior, APIs, domain boundaries, tests, security, workflows, dependencies, CI, documentation, or agent instructions. Do not use as the primary workflow for repository-wide technical-debt portfolio audits, implementation, active failure debugging, or design-only threat modeling.
Often used withclose-specadd-new-modelcompare-screenshots
tigu77Skilltigu77/tiguclaw/skills/code-review/SKILL.md
코드 변경(작업 트리 diff·브랜치·PR·경로·커밋 범위)을 **읽기 전용**으로 검토해, 실제로 확인한 발견만 보고한다. '리뷰해줘·검토해줘·이 diff 봐줘·PR 봐줘·머지해도 되나·이 수정 괜찮아?·내가 고친 거 다시 봐줘' 류 요청, 그리고 스스로 수정을 마친 뒤 되짚을 때. 버그 진단('이거 왜 안 돼')에도 같은 검사 축을 쓴다. 리뷰는 독립 매니저가 먼저 혼자 읽고, 파일이 많으면 **겹치지 않는 파일 묶음**으로만 나눈다(관점·발견 수로 나누지 않는다). 발견마다 한 동작으로 확인한 뒤에만 보고하고, 고치지 않는다 — 수정은 사용자가 따로 시킬 때 별도 단계다.
Often used withclose-specadd-new-modelcompare-screenshots
wpankSkillwpank/ai/skills/testing/code-review/SKILL.md
Systematic code review patterns covering security, performance, maintainability, correctness, and testing — with severity levels, structured feedback guidance, review process, and anti-patterns to avoid. Use when reviewing PRs, establishing review standards, or improving review quality.
Often used withclose-specadd-new-modelcompare-screenshots
z-ZihanSkillz-Zihan/Evir/skills/builtin/code-review/SKILL.md
Use on Desktop when reviewing a diff, commit, branch, or local code for correctness, regressions, security, performance, and maintainability.
Often used withclose-specadd-new-modelcompare-screenshots
conorbronsdonSkillconorbronsdon/agent-skills/code-review/SKILL.md
Multi-agent deep review for code PRs in any repo. Use when asked to "deep review this PR," "multi-agent review," "review #N with subagents," "thorough review of this branch," or "is this PR ready to merge." Orchestrates Copilot + parallel subagents (adversarial, operational, reference-comparison) with scope-based escalation, stale-finding triage, and a hard iteration cap.
Often used withclose-specadd-new-modelcompare-screenshots
flightctlSkillflightctl/ai-workflows/code-review/SKILL.md
AI-driven code review workflow that reviews uncommitted changes using a discoverable reviewer profile, presents findings for human decision, and iterates until approved. Supports --unattended for automated iteration. Use when reviewing code before commit or PR. Activated by commands: /start, /continue, /clean.
Often used withclose-specadd-new-modelcompare-screenshots
kambleakash0Skillkambleakash0/agent-skills/skills/code-review/SKILL.md
Performs a thorough code review of the current changes or a specified file / pull request. Covers correctness, security, performance, readability, and adherence to project conventions. Outputs prioritised, actionable feedback. TRIGGER when the user writes /code-review or asks for a code review, PR review, or feedback on their code.
Often used withclose-specadd-new-modelcompare-screenshots
onlyoneamanSkillonlyoneaman/agent-skills/skills/code-review/SKILL.md
Reviews code for best practices, bugs, security issues, and provides improvement suggestions
Often used withclose-specadd-new-modelcompare-screenshots
PedroMosqueraSkillPedroMosquera/squadai/.agents/skills/code-review/SKILL.md
Structured code review with severity-based findings
Often used withclose-specadd-new-modelcompare-screenshots
pekralSkillpekral/cursor-rules/skills/code-review/SKILL.md
Use when senior PHP code review focused on architecture, business
Often used withclose-specadd-new-modelcompare-screenshots
botlearn-aiSkillbotlearn-ai/botlearn-skills/skills/code-review/SKILL.md
name: code-review role: Code Review Specialist version: 1.0.0 triggers: - "review code" - "code review" - "check this code" - "find bugs" - "security audit" - "review my code" - "check for vulnerabilities" - "code quality" --- # Role
Often used withclose-specadd-new-modelcompare-screenshots
CodePhobiiaSkillCodePhobiia/claude-roblox-game-studio/.claude/skills/code-review/SKILL.md
Review Luau code for style compliance, type safety, server authority, error handling, and performance. Use for reviewing a file, a PR-sized change, or a whole module.
Often used withclose-specadd-new-modelcompare-screenshots
E4crypt3dSkillE4crypt3d/oh-my-qwen/skills/code-review/SKILL.md
Systematic code review with structured output and actionable findings. Use when reviewing code, auditing quality, checking for bugs, security vulnerabilities, or performance issues.
Often used withclose-specadd-new-modelcompare-screenshots
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Open a skill to see its discussion. Reports from people and their agents are coming.
