Code Review
Automated code review and analysis
receiving-code-review
by alffei
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
using-git-worktrees
by alffei
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
executing-plans
by alffei
Use when you have a written implementation plan to execute in a separate session with review checkpoints
subagent-driven-development
by alffei
Use when executing implementation plans with independent tasks in the current session
using-superpowers
by alffei
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
java25-springboot4-reviewer
by a-pavithraa
Comprehensive code review for Java 25 and Spring Boot 4 apps. Use when reviewing, checking, auditing, or analyzing Java/Spring Boot code (files, modules, PRs, or full codebases) for migration risks, Spring Boot 4 best practices, JSpecify null-safety, security vulnerabilities, performance bottlenecks, data access pitfalls, architecture boundaries (DDD/Hexagonal/Spring Modulith), or modern Java 25 usage.
bug-reaper
by shaniidev
"Web2 bug bounty hunting agent — evidence-based vulnerability finder and report writer. Use when: auditing web apps/APIs for HackerOne, Bugcrowd, Intigriti, YesWeHack; hunting XSS, SQLi, NoSQLi, SSRF, IDOR, auth bypass, RCE, SSTI, LFI, XXE, CORS, CSRF, prototype pollution, subdomain takeover, HTTP smuggling, open redirect, API/GraphQL bugs; auditing locally downloaded GitHub repos or source code (white-box/source code review); writing platform-specific reports. Trigger on: 'pentest', 'find bugs', 'security audit', 'bug bounty', 'find vulnerabilities', 'source code review', 'audit this repo', 'review repo', 'white-box', 'local repo', vulnerability class names, or program/target names. Reports only real, confirmed medium+ severity bugs that pass real triage."
gh-version-control-workflow
by robertmsale
Run a disciplined GitHub workflow with git + gh using issues, issue-derived branches, worktrees, and PRs. Use when you need concurrent feature work, clear review boundaries, and issue-linked PRs instead of direct commits to integration branches.
agent-orchestrator-standalone
by mrclrchtr
Orchestrate complex work via a phase-gated multi-agent loop (audit → design → implement → review → validate → deliver). Use when you need to split work into subsystems, run independent audits, reconcile findings into a confirmed issue list, delegate fixes in clusters, enforce PASS/FAIL review gates, and drive an end-to-end validated delivery. Do not use for small, single-file tasks.
request-review
by robertmsale
Request code review and route results to a tmux pane. Default flow commits first; optional opt-in flow can target an existing commit without commit/push.
workleap-skill-safety-review
by workleap
Evaluate third-party agent skills for security risks before adoption or update. Use when: (1) Installing or updating a skill from skills.sh, ClawHub, or any public registry, (2) Auditing skills for security risks or reviewing PRs that add/update skill dependencies, (3) Building a team/org allowlist of approved skills, (4) Investigating suspicious skill behavior or answering "is this skill safe?" / "should we adopt this skill?"
feature-writing
by sotayamashita
Review and write feature announcements using a 4-part framework (Context, Solution, Usage, Resources). Use when writing or reviewing blog posts, release notes, changelogs, customer emails, internal comms, product updates, or feature marketing content. Covers problem-led messaging, benefit-focused language, audience tone matching, and scannable structure. Triggers on any task involving feature descriptions, product announcements, or upgrade communications.
critical-partner
by joabgonzalez
"Rigorous code review and improvement partner. Trigger: When validating code quality, reviewing implementations, or providing critical feedback."
workleap-chromatic-best-practices
by workleap
Workleap's Chromatic best practices for snapshot cost control and CI optimization. Use this skill when: (1) Auditing or implementing Chromatic cost optimizations in a repository (2) Fixing Chromatic TurboSnap-disabling patterns (barrel imports, large preview dependencies, local scripts) (3) Setting up or updating chromatic.config.json and GitHub Actions CI workflows for Chromatic (4) Reviewing PRs for Chromatic snapshot cost impact (5) Configuring Chromatic in Turborepo/monorepo projects
assign-agent
by robertmsale
Launch delegated Codex workers in dedicated tmux sessions via codex-tmux, with resumable CODEX_THREAD_ID handoff for GitHub issue workflows.
skill-optimizer-yashu
by steelan9199
分析并优化其他 Skill 的文档质量问题，包括 frontmatter 格式、渐进式披露结构、文件引用完整性、AI 友好性等检查。何时使用：当用户说"优化这个 skill"、"检查 skill 质量"、"review skill"、"skill 有问题"、"帮我看看这个 skill"、"诊断 skill"时。
accessibility-audit
by mgd34msu
"Load PROACTIVELY when task involves accessibility compliance or inclusive design. Use when user says \"check accessibility\", \"audit for WCAG\", \"fix screen reader issues\", \"add keyboard navigation\", or \"check color contrast\". Covers WCAG 2.1 AA compliance across semantic HTML, ARIA patterns, keyboard navigation, screen reader support, color contrast ratios, form accessibility, media alternatives, and focus management. Produces structured audit reports with severity ratings."
safe-delete
by robertmsale
Use the trash CLI for deletions so files are recoverable. Prefer this skill whenever a task involves removing files or directories.
agent-orchestrator
by mrclrchtr
Orchestrate complex work via a phase-gated multi-agent loop (audit → design → implement → review → validate → deliver). Use when you need to split work into subsystems, run independent audits, reconcile findings into a confirmed issue list, delegate fixes in clusters, enforce PASS/FAIL review gates, and drive an end-to-end validated delivery. Do not use for small, single-file tasks.
ab-test-setup
by boisenoise
"Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness."
ux-writing
by sotayamashita
Review and write UI text following Material Design 3 UX writing best practices. Use when writing new UI text (buttons, labels, dialogs, error messages, notifications, titles, menus, tooltips, empty states, form fields) or reviewing and fixing existing UI text for clarity, consistency, and accessibility. Covers sentence case, word choice, grammar, punctuation, pronouns, abbreviations, and consequence communication. Triggers on any task involving microcopy, interface copy, UI strings, or UX text.
getting-started-guide
by wordflowlab
"Activates when users start a new novel project - guides them through the seven-step methodology (constitution → specify → clarify → plan → tasks → write → analyze) with gentle prompts and explanations"
health-check
by acedergren
"Run all quality gates across the entire codebase and report results. Headless — no analysis, just execute and print. Use for pre-PR validation, phase completion, or routine health monitoring."
implement
by acedergren
"Full feature pipeline — pre-flight checks, TDD cycle, scope guard, quality commit. Combines pre-flight + tdd + scope-check + quality-commit into one flow. Use when implementing a feature, adding an endpoint, or building any non-trivial code change."