Inspect and evaluate GitHub PR review comments, respond with a clear technical position, and implement only valid feedback. Use when asked to review PR comments, respond to reviewers, address reviewer feedback, or make changes based on PR feedback.
Run Matt Shumer's Gauntlet Loop methodology to raise the quality of an artifact through cycles of building, independent critique, comparison against real references, and improvement. Use when the user asks for the Gauntlet Loop, a builder-critic process, adversarial critique, iterative refinement, or the creation of…
A reviewer for automated agent or workflow projects, based on the Loop Engineering rules by Addy Osmani. It checks whether creation and review are separated, whether pass conditions are objective, and whether the loop has limits and human approval points.
Two-phase PR review companion. Phase 1: Socratic conversational walkthrough that builds the reviewer's mental model through guided questions — fighting cognitive debt by ensuring comprehension before approval. Phase 2: automated quality checks via pr-review-toolkit (Claude Code) or inline review (any host). Use when…
Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.
Run a repository story through two isolated Codex sessions, with one implementer working in a Git worktree and one independent reviewer inspecting the branch, followed by a bounded fix pass, deterministic verification, and a human PR and merge gate. Use when the user explicitly asks for a dual-agent Codex workflow, an…
Review the current diff against path-scoped rules (secrets, RLS/tenant scoping, Stripe webhook verification, input validation, scope), flag changed code lacking tests, and run a quick security pass. Reports findings; nothing auto-fixed without approval.
Run boundary and structure validators against a Hydrogen storefront project. Reports cross-module imports, reverse imports from shared layers, dumping-ground folders, barrel files, forbidden Remix imports, and missing/duplicated route manifests.
Coordinates a subagent workflow where a worker implements a development task, a code reviewer audits the result for critical errors, flaws, and optimization opportunities, and then the worker iterates to apply the reviewer’s optimization suggestions. Use when the user requests implementation or other development work…
Codex Adversarial Review - Lite: user-invoked audit workflow for Claude Code users who want Codex CLI to independently review AI-generated code, plans, test expectations, and scope before fixes are applied. Cross-platform (Windows, macOS, Linux, WSL). Use only when the user explicitly invokes audit or selftest.
Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns.
Use when asked to proofread, review, or 校对 code or documents for correctness, logical consistency, or quality issues. Covers general code logic review (any language), plus formal-verification backends for C (ACSL contracts via Frama-C static proof and E-ACSL runtime checks), Python (icontract + CrossHair), Rust (Kani…
Dispatch a review to the Bridge, which resolves the reviewer Lane from this machine's Machine Config. Use when a review is asked for without naming a lane, or when a review-skill invocation was refused and pointed here.
Use when reviewing or writing code that contains Russian-language UI strings, i18n locale files (ru.json, ru.yml, ru.po), Russian comments, or transliterated identifiers (polzovatel, tovar, kolichestvo). Triggers on mixed English-code + Russian-content projects. Does not cover typography, spelling, or ё/е.
Use when the user wants to review a pull request, understand what a PR changes, assess risk of merging, or check for missing test coverage. Examples: "Review this PR", "What does PR #42 change?", "Is this PR safe to merge?".
Adversarial collaborator who pushes back like a senior engineer - the default adversarial reviewer. Surfaces hidden assumptions, grounds every challenge in evidence, presents real counterpoints with proven alternatives, drives toward synthesis, and records settled claims as verdict nodes in docs/verdicts/ so an…
★not rated 1
changed 3d agoA193 tokens
originalMIT
Use when reviewing a pull request or branch diff with fixed perspectives and unified findings. Orchestrates code-reviewer, silent-failure-hunter, pr-test-analyzer, comment-analyzer, type-design-analyzer, and code-simplifier viewpoints.
Fully automatic GitHub PR review and production deployment gate for trusted repos. Use when configuring or operating a scheduled PR gate that checks open PRs, downloads them locally, runs complete containerized validation with mocked external services, comments or rejects failing PRs, promotes passing PRs through…
Review a Codex, Claude Code, or agent skill/plugin before public release. Use when the user wants to assess trigger quality, folder structure, documentation, validation gaps, GitHub readiness, or OSS release quality for an agent extension.
Multi-perspective code review with breaking-change detection, a deterministic merge gate, and questions for the dev. Spawns 6 parallel reviewers. Output optimized for PR-thread copy/paste — GitHub, GitLab, or Azure DevOps (emoji semaphore, lists, backticked code).
Scan a repository against curated coding standards and produce a structured audit report, issue set, refactor plan, and sprint-based remediation roadmap. Use when the user invokes /vibe.audit or asks to review the codebase against established rules. Operates in full autopilot mode from repository scan to sprint plan…
★not rated 1 2d agoA68 tokens
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: