19,479 mods in this category, of every kind an
agent can take. Each one carries what it costs per session, what the
scan found, and whether it is the original.
Harvests offline documentation (README, CHANGELOG, public API) for every gem in a Ruby/Rails project's Gemfile.lock into a local cache, tracks gem versions in a manifest, and refreshes only gems whose version changed. Then reviews a git diff or pull request against that cache to surface (a) gem-upgrade impact …
This skill should be used when the user asks for a code review of a change — a pull request, merge request, branch, commit range, working-tree change, or pasted diff — covering correctness, security, performance, structure, and repository-specific rules. Trigger on phrases like "review this PR", "review this MR"…
Assesses a legacy .NET codebase and produces a pragmatic, incremental modernization roadmap — from .NET Framework to modern .NET, monolith to modular, and toward testability, DI, async, and current patterns — prioritized by risk and value. Use when the user wants to modernize legacy code, migrate from .NET Framework…
Comprehensive Nushell scripting best practices, idioms, security, and evidence-driven code review. Use when writing, reviewing, auditing, debugging, or refactoring Nushell (.nu) scripts, modules, custom commands, pipelines, config, and tests. Also use for Bash/POSIX-to-Nushell conversion and Nu migration issues…
Four agent skills for Playwright and Cypress end-to-end tests: generate new Playwright specs through the installed official Playwright agents with a short rules checklist and a scanner gate, review existing specs or PR diffs, and debug failed runs.
★not rated 26▲
+3
changed yesterdayA
tokens not measured
originalApache-2.0
Interactive remediation of code review findings using parallel specialist agents. Elicits user input at key decision points (use --quick to skip prompts), deploys domain specialists, and verifies with pr-review-toolkit.
Run a full-spectrum, multi-agent audit covering every layer of the application: architecture, implementation, testing, security, frontend/UX, product alignment, and blind code review. All rounds run in parallel — contamination is prevented by instruction, not by timing. Phase 2 begins only after all active rounds…
Claude Code plugin for whitebox security review. Stable: deterministic offline quick scan, shared findings.json with stable keys and hotspot-aware findings, SARIF/Markdown/HTML/bundle reports, suppressions, CI fail-on gate, Kuzushi parity. Beta: deep profile with Joern/CodeQL/Slither/Trivy/Checkov when installed.…
★not rated 25 4mo agoA
tokens not measured
originalMIT
Run Aperture Lab F-Stop on imported public trajectories, prepare review artifacts, compare disagreements, and propose bounded semantic-layer improvements under strict replay gates.
Analyzes Move language packages against the official Move Book Code Quality Checklist. Use this skill when reviewing Move code, checking Move 2024 Edition compliance, or analyzing Move packages for best practices. Activates automatically when working with .move files or Move.toml manifests.
Review a specific GitHub pull request with gh — fetch the diff, fan out reviewers, consolidate, and optionally post the review. Requires the gh CLI or the GitHub MCP server.
Review MCP server specifications and updates for compliance, security, and quality. Use when evaluating server.json files, PRs adding/updating servers, or assessing MCP server changes. NOT for creating new entries (use add-mcp-server instead).
A coordination skill for handing an implementation plan to a separate coding process or remote machine, then tracking its progress. It uses the handoff command-line tool and supports independent executors such as Claude, Codex, or OpenCode.
Teaches an AI agent to use grafel MCP tools as a structural second pair of eyes during code review. Covers impact radius analysis, orphan detection, dead-end flow discovery, cross-repo consistency checks, and pattern violation spotting — with a per-change-type tool sequence, a severity rubric, and worked examples.
Logic-first code review using semi-formal execution tracing. Surfaces behavioral bugs, type contract breaches, boundary blindspots, and interprocedural semantic mismatches — the logic errors that cause production incidents in syntax-clean code.
★not rated 25
changed 8d agoA
tokens not measured
originalMIT
Standalone code review for any scope — PR number, branch, file paths, or current changes. Synthesizes intent, runs 13 parallel specialized agents, plus one that checks rule consistency when instruction files change, and presents actionable findings with a verdict. A dependency update (Dependabot, Renovate, any…
A questioning guide for examining whether a software design uses the right abstractions. Abstraction means grouping related ideas while keeping unrelated parts separate.
★not rated 24 6mo agoA172 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: