Code Review
Automated code review and analysis
receiving-code-review
by izyanrajwani
Assesses and responds to incoming code review feedback on PRs (reviewer comments, requested changes), especially when suggestions are unclear, technically questionable, or scope-expanding. Use before implementing review suggestions to align on intent and keep changes minimal.
executing-plans
by izyanrajwani
Disciplined plan execution for implementation tasks. Use when executing a saved implementation plan, following step-by-step instructions from a plan document.
eth-rnd-archive
by lodekeeper
Track and summarize discussions from ethereum/eth-rnd-archive across selected Discord channels, with hourly monitoring and daily digest outputs. Use for protocol/R&D intelligence, spotting spec changes, and surfacing Lodestar-relevant action items from Eth R&D chatter.
cli-just
by PaulRBerg
This skill should be used when the user asks to "create a justfile", "write just recipes", "configure just settings", "add just modules", "use just attributes", "set up task automation", mentions justfile, just command runner, or task automation with just.
spec-kit-implement
by ahgraber
Use when approved Spec Kit tasks.md must be executed into implementation changes, or when task execution is blocked by sequencing/checklist gates before feature completion.
oracle-codex
by PaulRBerg
This skill should be used when the user asks to "use Codex", "ask Codex", "consult Codex", "use GPT for planning", "ask GPT to review", "get GPT's opinion", "what does GPT think", "second opinion on code", "consult the oracle", "ask the oracle", or mentions using an AI oracle for planning or code review. NOT for implementation tasks.
spec-kit-analyze
by ahgraber
Use when spec.md, plan.md, and tasks.md exist and you need a read-only Spec Kit audit for consistency, requirement-to-task coverage, ambiguity, duplication, or constitution conflicts before implementation.
coderabbit
by PaulRBerg
This skill should be used when the user asks to "review CodeRabbit feedback", "triage CodeRabbit comments", "check CodeRabbit PR review", "evaluate CodeRabbit suggestions", "process CodeRabbit review", "address CodeRabbit comments", "fix CodeRabbit issues", "coderabbit review", or mentions reviewing, triaging, or acting on CodeRabbit bot feedback on a pull request.
kurtosis-devnet
by lodekeeper
Run Ethereum multi-client devnets using Kurtosis and the ethpandaops/ethereum-package. Use for spinning up local testnets, validating cross-client interop, testing fork transitions, running assertoor checks, debugging CL/EL client interactions, or verifying new feature implementations across multiple consensus and execution clients.
pull-request-review
by alexanderguy
Review a pull request by branch name or URL, using a git worktree
ls-lint
by PaulRBerg
This skill should be used when the user asks to "configure ls-lint", "set up filename linting", "enforce naming conventions", "create .ls-lint.yml", "lint file names", "lint directory names", "file naming rules", "directory structure linting", or mentions ls-lint, directory naming rules, or filename conventions.
things-morning-organizer
by apocohq
"Morning review and prioritization of Things todos. Use this skill every morning, or whenever the user asks to review, triage, categorize, or prioritize their Things tasks. Also trigger when the user says things like 'what should I work on today', 'organize my todos', 'morning routine', or 'daily review'."
commit-message
by ahgraber
"Use when drafting a Conventional Commit message from currently staged Git changes. Triggers: 'write commit message', 'draft commit from staged changes', 'generate conventional commit', 'message for git commit -F -'. Not for creating commits, amending history, or full code review."
code-review
by PaulRBerg
This skill should be used when the user asks to "review code", "review PR", "code review", "audit code", "check for bugs", "security review", "review my changes", "find issues in this code", "review the diff", or asks for pull request review or code audit.
requesting-code-review
by izyanrajwani
Use when you need to request a code review for a PR/MR and want a consistent review brief (context, scope, risk areas, test instructions, acceptance criteria) before merge.
code-polish
by PaulRBerg
This skill should be used when the user asks to "polish code", "simplify and review", "clean up and review code", "full code polish", "simplify then review", "refactor and review", "simplify and fix", "clean up and fix", or wants a combined simplification and review workflow on recently changed code.
android-use
by shehbajdhillon
Control Android devices via ADB commands - tap, swipe, type, navigate apps
multi-agent-orchestration
by PeterFile
Orchestrate multi-agent workflows from a Kiro spec using codex (code) + Gemini (UI), including dispatch/review/state sync via AGENT_STATE.json + PROJECT_PULSE.md; triggers on user says "Start orchestration from spec at <path>", "Run orchestration for <feature>", or mentions multi-agent execution.
magento-upgrade-specialist
by maxnorm
Manages seamless Magento 2 version upgrades and migrations. Use when upgrading Magento versions, migrating from Magento 1, planning upgrade strategies, assessing compatibility, or handling breaking changes. Masters upgrade planning, compatibility assessment, and post-upgrade optimization.
publishing-platforms
by pluginagentmarketplace
Platform submission processes, certification requirements, and distribution across Steam, Epic, console, and mobile platforms.
optimization-performance
by pluginagentmarketplace
Game optimization, performance profiling, multi-platform support, and frame rate optimization for smooth gameplay experiences.
agent-tower-plugin
by BayramAnnakov
Multi-agent deliberation for Claude Code - orchestrate AI coding assistants (Claude, Codex, Gemini) for council, debate, and consensus workflows
graphics-rendering
by pluginagentmarketplace
3D graphics, shaders, VFX, lighting, rendering optimization. Create stunning visuals with production-ready techniques.
mergeability-gate
by OmniNode-ai
Evaluate a PR's mergeability and label it appropriately. Outputs one of three statuses — mergeable, needs-split, or blocked — called by ticket-pipeline between local_review and create_pr phases.