- Home
- /
- Categories
- /
- Code Review
Code Review
Automated code review and analysis
paper-validator
by minhuw
This skill should be used when conducting comprehensive reviews of research papers for top-tier computer science conferences. Use for identifying weaknesses, unclear statements, missing evidence, and structural issues in academic papers. The skill autonomously reads files, searches for patterns, analyzes structure, and provides constructive peer-reviewer feedback.
interview
by abatilo
Interview users in-depth about their plans using probing, non-obvious questions. Use when user says "/interview", "interview me", "question my plan", "probe my idea", "challenge my assumptions", or wants deep exploration of a plan before implementation.
ultra-review
by rocky2431
"Parallel code review orchestration with 6 specialized agents + coordinator. Zero context pollution - all output via JSON files."
charted-review
by marmicode
Reviews a design doc with expert sub-agents
evaluate
by minhuw
This skill should be used when evaluating the logical flow, structure, readability, and overall quality of research paper text. Use for assessing academic writing targeting top-tier computer science conferences.
algo-sensei
by karanb192
Your personal DSA & LeetCode mentor. Use for problem explanations, progressive hints, code reviews, mock interviews, pattern recognition, complexity analysis, and custom problem generation. Automatically adapts to your learning style and request type.
personal:mole
by shiqkuangsan
"Mac 深度清理优化命令顾问。根据需求输出可复制的 mo 命令,辅助磁盘分析和配置管理。触发词:mole、mo、清理Mac、磁盘空间、系统优化、卸载App"
oss-security-audit
by backnotprop
Audits the CI/CD pipeline, repository, release process, automations, and dependency hygiene of an open-source software supply chain, then produces an elegant HTML report of findings and recommendations. Use this skill whenever the user asks to assess, audit, review, harden, or evaluate the security of a repository, its GitHub Actions or GitLab CI pipelines, its release process, its supply chain, or its overall security posture — even if they don't use the word "audit." Also trigger on phrases like "is this repo secure," "check our CI," "supply chain review," "harden our release," "review our workflows," or when a user points at a repo and asks what they should fix.
syncause-debugger
by Syncause
Diagnose and fix bugs using runtime execution traces. Use when debugging errors, analyzing failures, or finding root causes in Python, Node.js, or Java applications.
security-audit
by iskysun96
"Audits Move contracts for security vulnerabilities before deployment using 7-category checklist. Triggers on: 'audit
supabase-audit-tables-read
by yoanbernabeu
Attempt to read data from exposed tables to verify actual data exposure and RLS effectiveness.
agent-native-reviewer
by ratacat
"Use this agent when reviewing code to ensure features are agent-native - that any action a user can take, an agent can also take, and anything a user can see, an agent can see. This enforces the principle that agents should have parity with users in capability and context. <example>Context: The user added a new feature to their application.\nuser: \"I just implemented a new email filtering feature\"\nassistant: \"I'll use the agent-native-reviewer to verify this feature is accessible to agents\"\n<commentary>New features need agent-native review to ensure agents can also filter emails, not just humans through UI.</commentary></example><example>Context: The user created a new UI workflow.\nuser: \"I added a multi-step wizard for creating reports\"\nassistant: \"Let me check if this workflow is agent-native using the agent-native-reviewer\"\n<commentary>UI workflows often miss agent accessibility - the reviewer checks for API/tool equivalents.</commentary></example>"
feature-video
by ratacat
Record a video walkthrough of a feature and add it to the PR description
agent-native-audit
by ratacat
Run comprehensive agent-native architecture review with scored principles
deployment-verification-agent
by ratacat
"Use this agent when a PR touches production data, migrations, or any behavior that could silently discard or duplicate records. Produces a concrete pre/post-deploy checklist with SQL verification queries, rollback procedures, and monitoring plans. Essential for risky data changes where you need a Go/No-Go decision. <example>Context: The user has a PR that modifies how emails are classified. user: \"This PR changes the classification logic, can you create a deployment checklist?\" assistant: \"I'll use the deployment-verification-agent to create a Go/No-Go checklist with verification queries\" <commentary>Since the PR affects production data behavior, use deployment-verification-agent to create concrete verification and rollback plans.</commentary></example> <example>Context: The user is deploying a migration that backfills data. user: \"We're about to deploy the user status backfill\" assistant: \"Let me create a deployment verification checklist with pre/post-deploy checks\" <commentary>Backfills are high-risk de..."
design-iterator
by ratacat
"Use this agent PROACTIVELY when design work isn't coming together on the first attempt. If you've made 1-2 design changes and the result still feels off, suggest using this agent with 5x or 10x iterations for deeper refinement. This agent takes screenshots, analyzes what's not working, implements improvements, and repeats N times to systematically fix design issues. Perfect when colors feel wrong, layouts aren't balanced, or the overall aesthetic needs work that single changes can't achieve. <example>Context: User asks to change button color but result still looks off. user: \"Change the button to blue\" assistant: [makes change, takes screenshot] \"The button is now blue, but I notice the overall color balance still feels off. Would you like me to use the design-iterator agent with 5 iterations to systematically improve the color harmony and visual balance?\" <commentary>PROACTIVE USE: After a simple change doesn't fully resolve the design issue, suggest the design-iterator to do deeper work.</commentary></ex..."
framework-docs-researcher
by ratacat
"Use this agent when you need to gather comprehensive documentation and best practices for frameworks, libraries, or dependencies in your project. This includes fetching official documentation, exploring source code, identifying version-specific constraints, and understanding implementation patterns. <example>Context: The user needs to understand how to properly implement a new feature using a specific library. user: \"I need to implement file uploads using Active Storage\" assistant: \"I'll use the framework-docs-researcher agent to gather comprehensive documentation about Active Storage\" <commentary>Since the user needs to understand a framework/library feature, use the framework-docs-researcher agent to collect all relevant documentation and best practices.</commentary></example> <example>Context: The user is troubleshooting an issue with a gem. user: \"Why is the turbo-rails gem not working as expected?\" assistant: \"Let me use the framework-docs-researcher agent to investigate the turbo-rails documentation..."
cache-audit
by ussumant
Audit your Claude Code setup against prompt caching best practices. Checks ordering, tool stability, dynamic content handling, and hook injection patterns. Returns a scored report with specific fixes.
sanity-check
by ElliotJLT
Before building on assumptions, validates them first. Activates when making claims about how code works, what exists, or why something happens. Prevents assumption cascades where one wrong guess leads to a completely wrong solution.
fan-out
by ElliotJLT
Orchestration pattern for parallelizable tasks. When facing work that can be split into independent subtasks (research multiple topics, analyze multiple files, test multiple scenarios), spawn parallel agents and aggregate results. Use when subtasks have no dependencies on each other.
vcp-review-tests
by Z-M-Huang
Review test quality against VCP testing standards. Checks for tautological tests, over-mocking, missing edge cases, and other anti-patterns.
color-contrast
by dylantarre
Validates WCAG 2.1 contrast ratios and generates accessible color pairings. Use when checking accessibility compliance, fixing contrast issues, or selecting text/background combinations for AA or AAA levels.
vcp-pre-commit-review
by Z-M-Huang
Review staged/changed files against all applicable VCP standards before committing. Produces a PASS/BLOCK verdict. Run this before every commit.
dependency-tracker
by blessonism
Track and check updates for all OpenClaw dependencies: managed skills (GitHub/ClewHub), bundled skills, workspace skills, npm packages, pip packages, and CLI tools. Use when user asks "check for updates", "dependency status", "are my skills up to date", "什么需要更新", "检查依赖", "检查更新", or wants a dependency health report. Triggers on: dependency check, skill updates, outdated packages, version drift.