Review frontend code under `web/` or `packages/dify-ui/` when the user explicitly requests a review or audit. Supports PRs, branches, pending changes, files, and pasted diffs. Do not use for implementation-only requests, diagnosis without review intent, or backend-only code.
Review or re-review a Docling pull request with reproducible findings and explicit validation results. Use for code, tests, dependencies, documentation, or agent guidance.
Use when reviewing uncommitted changes, a branch, or a pull request for dsh-web. Focuses on correctness, plugin boundaries, browser behavior, security, generated artifacts, and missing evidence.
10k7d agoReviewMountCreate a free account to mount
Perform evidence-based reviews of PRs, commits, patches, files, issue fixes, designs, or implementation plans. Use for code review, risk and compatibility analysis, test coverage review, and verifying reported bugs or requirements before evaluating a change.
Run the CI Codex PR review locally against this branch's unpushed work (committed + uncommitted) before pushing. Same policy, model and reasoning effort as the codex-pr-review GitHub action.
Steady8 mentions in 2 weeks
No other project uses it yet
18k12d agoReviewMountCreate a free account to mount
PostgreSQL-specific code review assistant focusing on PostgreSQL best practices, anti-patterns, and unique quality standards. Covers JSONB operations, array usage, custom types, schema design, function optimization, and PostgreSQL-exclusive security features like Row Level Security (RLS).
3 projects use a version of this
41k20d agoReviewMountCreate a free account to mount
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. Use when asked to review a diff or a pull request, even when the diff is pasted inline.
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
96k22d 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.
13k11d 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.
Surging5 mentions in 2 weeks
7 projects use a version of this
10k12d 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.