Adversarial senior review of the spec before any code is written. Constructs a skeptical reviewer whose authority comes from the codebase, §R research, and live best-practice — then tries to REFUTE the spec, not rubber-stamp it. Every finding cites evidence (file:line or source); unverifiable ones are flagged. Survivors harden §V; the run ends in an explicit go / no-go gate. Triggers before building anything high-blast-radius, when the user says "review the spec", "red-team this", "is this plan sound", "senior review", or invokes /ck:review.
Review and improve the code comments a PR or branch adds, against the standard in docs/developer/CODE_COMMENTS.md: cut the ones that restate the code, tighten the verbose ones, reframe what-comments into the why or the constraint, and add the contract docs the change left missing. Runs comment-lint for the mechanical rules first, then judges what a linter cannot: padding around one real fact, facts already stated by a type or a name, comments that will go stale on the next unrelated change, and new public surfaces left undocumented. Applies comment-only edits and reports every verdict in chat. Use when asked to review, clean up, trim, thin out or improve the comments on a PR or branch, to strip AI-looking narration before requesting review, or when comment-lint findings need judgment rather than a mechanical fix. Pass --report-only to change nothing.
3 projects use a version of this
96k23d agoReviewMountCreate a free account to mount
Maintainer-grade code review for COLMAP (C++, CUDA/HIP, pycolmap, CMake, and benchmarks): checks geometric and numerical correctness, modularity and readability, memory/binding safety, performance, and test quality, while shrinking bloat, reusing existing helpers, and localizing changes. Use for "review this", "code review", "review the last commit", "review my PR", "can this diff be smaller", or "is this over-engineered". Don't use when asked to implement changes or run benchmarks directly.
Steady9 mentions in 2 weeks
No other project uses it yet
13k12d agoReviewMountCreate a free account to mount
Use this skill when a repository already has an open pull request and you need to run the Coder Agents Review loop: request review with `/coder-agents-review` when needed, wait for feedback from the `coder-agents-review` GitHub app, fix issues, and repeat until the app approves (an `approved` comment or an `APPROVED` review).
17k32d agoReviewMountCreate a free account to mount
Runs a Greptile CLI review for the current local branch, installing or authenticating the CLI when needed, then summarizes JSON findings for the user. Use when the user wants Greptile feedback before opening a PR, outside a hosted PR review flow, or directly from a local checkout.
Surging3 mentions in 2 weeks
7 projects use a version of this
10k12d agoReviewMountCreate a free account to mount
Use when requesting independent code review, after implementation slices, before merging high-risk work, or when verification exposes evidence, baseline, architecture, compatibility, or retirement uncertainty.
Reviews a reverse-skill case package for scope readiness, Evidence to Finding to Path traceability, work item coverage, timeline references, and optional artifact hash integrity before report handoff.
40k54d agoReviewMountCreate a free account to mount
Review code changes or PRs for quality, correctness, and reviewability. Use when asked to "review", "check", "provide feedback", or "post a review". Dispatches specialized agents in parallel for thorough analysis.
33k8mo agoReviewMountCreate a free account to mount
Perform comprehensive code reviews for TypeScript projects, analyzing type safety, best practices, performance, security, and code quality with actionable feedback
Steady2 mentions in 2 weeks
No other project uses it yet
9.1k8mo agoReviewMountCreate a free account to mount
Review agent-written changes before merge, after substantial edits, or when re-reviewing a repair. Use the adversarial protocol for high-risk changes or an explicitly requested deep review.
29k49d agoReviewMountCreate a free account to mount
name: skill-doli-code-review
description:
Reviews Dolibarr PHP code for compliance with coding standards and security best practices, and fixes identified issues.
Use when the user asks to review
No other project uses it yet
7.8k17d agoReviewMountCreate a free account to mount
Adversarial dual-model code review that runs two AI models in parallel, cross-references findings, and produces a consensus severity table with fix confidence ratings. Use when asked for a thorough code review, adversarial review, dual-model review, confidence-rated review, or 'Hanselman review'.
1 project uses a version of this
2.2k10d agoReviewMountCreate a free account to mount
Review Xtensa assembly code for ESP32 platforms. Checks for critical errors in inline assembly, ABI compliance, and optimization opportunities. Use after modifying ESP32 assembly or inline asm code.
Steady4 mentions in 2 weeks
No other project uses it yet
7.5k53d agoReviewMountCreate a free account to mount
Review a PR for correctness, security, code quality, and testing issues. TRIGGER when user asks to review a PR, check PR quality, or give feedback on a PR.
Steady5 mentions in 2 weeks
195 projects use a version of this
188k11d agoReviewMountCreate a free account to mount
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.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
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.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.
JuliusBrusseeSkill
