39,510 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.
Review code changes with GitNexus from a GitHub PR URL or number, a branch/ref or commit range, or local staged, unstaged, and untracked changes. Use when the user asks for a code review, merge-risk assessment, regression hunt, missing-test analysis, or a verdict on whether a PR, branch, commit range, or local diff is…
You are the GitNexus PR review coordinator. Review the pull request named after this command (a PR URL or number for https://github.com/abhigyanpatwari/GitNexus). If none was given, ask for one.
Assesses an open Dependabot pull request and emits a recommendation (Merge / Review before merging / Do not merge) plus confidence (High / Medium / Low) with concise prose grounded in upstream source changes. Advisory only: it posts a single comment and never merges, approves, or labels. Designed to run as a scheduled…
Review the current branch's changes for code quality, test coverage, security, best practices, and product/API alignment. Use when asked to perform a code review.
Address all valid review comments on a PR for the current branch in the streamlit/streamlit repo. Covers both inline review comments and general PR (issue) comments. Use when a PR has reviewer feedback to address, including code changes, style fixes, and documentation updates.
End-to-end review of a CCXT pull request. Reads the diff, transpiles and builds in all six languages (TS/JS, Python, PHP, C#, Go, Java), runs offline tests + live smoke tests, inspects both source and generated code, checks for security/performance/race-condition issues, drafts a structured review (verdict, inline…
Investigate a GitHub issue or pull request in colinhacks/zod and write up a durable verdict. Use whenever asked to triage, investigate, review, evaluate, or form an opinion on an issue or PR (by number, URL, or "the open PR queue"), and when sweeping many of them in bulk. For a draft SECURITY ADVISORY (a GHSA id, the…
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -…
Use this agent when you need to debug, reproduce, and fix GitHub issues reported for Chakra UI. This includes creating reproduction examples in the compositions app, tracing bugs through the codebase and dependencies (zag.js, ark-ui), and documenting fixes with changesets. Examples:\n\n \nContext: User provides a…
Plan and execute product isolation migrations to a facade plus contract layer in PostHog, following the Visual review architecture. Use when a product still exposes internals (models/logic/views) across boundaries and needs migration toward contracts.py + facade/api.py + presentation separation, with a PR strategy…
Finish GitHub pull requests for tinyhumansai/openhuman when the PR branch is ALREADY checked out locally (e.g. via the preem shell helper) with base merged in and upstream tracking set. Skips fetch/checkout/conflict-resolution; goes straight to collecting reviewer/bot feedback, applying every actionable fix, running…
Finish GitHub pull requests for tinyhumansai/openhuman by applying all actionable reviewer/bot feedback, committing fixes, and pushing back to the PR branch. Use when the user provides a PR URL or number and asks to review, address comments, clean up, or prepare a PR for merge. This agent executes the pending work …
CodeRabbit-style PR Review Specialist. Takes a GitHub PR URL/number, produces a thorough CodeRabbit-style review (walkthrough, change summary table, per-file analysis, actionable inline comments with concrete code suggestions, nitpicks), presents it to the user for confirmation, then APPLIES approved suggestions, runs…
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: