Code Review
Automated code review and analysis
openclawbrain
by jonathangu
TypeScript-first OpenClawBrain workspace for contracts, event flows, pack artifacts, activation, compiler logic, and learner-side pack assembly.
academic-deep-research
by MarjorieBroad
Transparent, rigorous research with full methodology — not a black-box API wrapper. Conducts exhaustive investigation through mandated 2-cycle research per theme, APA 7th citations, evidence hierarchy, and 3 user checkpoints. Self-contained using native SkillBoss platform tools (web_search, web_fetch, sessions_spawn). Use for literature reviews, competitive intelligence, or any research requiring academic rigor and reproducibility.
gas-gmail-cards
by whichguy
Gmail add-on and CardService specialist for Google Apps Script. Operates in 3 modes: code review, plan review, and advisory/Q&A. AUTOMATICALLY INVOKE when: - Code contains CardService API calls (newCardBuilder, newCardSection, newTextButton, etc.) - Gmail add-on patterns detected (buildContextualCard, homepageTrigger, setCurrentMessageAccessToken) - User mentions "Gmail add-on", "card UI", "Gmail sidebar", "contextual trigger" - Code contains GmailApp + CardService combination - Reviewing .gs files with appsscript.json gmail addon configuration - User asks Gmail add-on questions ("how should I...", "what's the best way...") - Plan/architecture discussions for Gmail add-ons Pattern Detection (triggers review): - CardService.newCardBuilder(), .addCard(), .buildHomepageCard() - GmailApp.setCurrentMessageAccessToken(), .getMessageById(), .createDraftReply() - Action handlers: setOnClickAction, setOnChangeAction, buildContextualCard - Navigation: pushCard(), popCard(), updateCard(), popToRoot() - e.gmail.accessToken, e.gmail.messageId, e.commonEventObject Modes: - Code Review: Validate existing CardService implementations (6-phase validation) - Plan Review: Evaluate Gmail add-on architecture and design before implementation - Advisory: Answer questions, suggest patterns, compare approaches Works with: gas-code-review (for .gs validation), gas-review (unified orchestrator) NOT for: HtmlService UIs (use gas-ui-review), Sheets-only GAS (use gas-code-review), Calendar/Drive/Docs add-ons (covered by gas-code-review)
gas-sidebar
by whichguy
Interactive GAS sidebar testing via Chrome DevTools. Launch sidebar, send prompts, read responses, manage config, and take screenshots -- all through MCP automation. AUTOMATICALLY INVOKE when: - User says "open sidebar", "launch sidebar", "test sidebar" - User says "send prompt", "send message", "chat with sidebar" - User says "check sidebar", "sidebar not working", "sidebar blank" - User wants to interact with Sheet Chat sidebar in any environment (Dev/Staging/Prod) - User says "gas-sidebar" or "/gas-sidebar" - User mentions "Sheet Chat" + any action verb (open, test, send, check) - User wants to verify sidebar deployment is working end-to-end MCP REQUIRED: chrome-devtools (with browserUrl for GAS auth), gas NOT for: Static code review (use /gas), server-side debugging (use /gas), symptom-based UI debugging without Chrome (use /gas)
conductor-status
by airclear
Provides a comprehensive status overview of the Conductor project. Use when the user wants to know the current progress, active tasks, next steps, or overall health of the project tracks and plans.
agents-md
by adampoit
Create and maintain AGENTS.md files that provide AI coding agents with project context, commands, code style, and boundaries. Use when updating an existing AGENTS.md, creating a new AGENTS.md for a repository, or improving agent instructions for a codebase.
gh-cli
by 1Mangesh1
GitHub CLI (gh) mastery for issues, PRs, releases, actions, gists, and repo management. Use when user asks to "create a PR", "list issues", "check CI status", "create a release", "view workflow runs", "create a gist", "clone a repo", "fork a repo", or any GitHub operations from the command line.
gas-plan
by whichguy
Dual-perspective GAS plan review (frontend + backend) with iterative convergence loop. AUTOMATICALLY INVOKE when: - Any plan exists for GAS changes, GAS project changes, or uses mcp_gas - Plan mode produces a plan file for a GAS project (scriptId present) - User says "review plan", "check plan", "validate plan", "plan review" - User says "is this plan ready", "plan quality", "gas-plan" - After ExitPlanMode on any GAS project plan - Plan references .gs files, .html files in GAS context, or mcp__gas__ tools - Plan modifies CommonJS modules, events, doGet/doPost, or addon code NOT for: Code review (use /gas-review), test review (use /gas-test-review), prompt analysis (use /prompt-critique), non-GAS plans mode parameter: - standalone (default): TeamCreate + parallel evaluators + convergence loop + ExitPlanMode - evaluate: Single-pass read-only evaluation — returns findings via SendMessage to calling team-lead. No edits, no team creation, no ExitPlanMode. Used internally by review-plan.
gas-code-review
by whichguy
PREFER OVER code-reviewer for GAS/Apps Script projects. Fast syntax and pattern validator. AUTOMATICALLY INVOKE when: - Code review, quality review, or validation in GAS context (scriptId present) - Reviewing .gs files in Apps Script projects - Detecting high-risk patterns: events, global, doGet/doPost/onOpen/onEdit - Before commits on GAS projects - User says "review", "check", "validate", "quality" with GAS code - Code snippet pasted containing: _main, defineModule, require(), module.exports ALWAYS PAIR WITH: gas-ui-review when .html files are also present (or use /gas-review for both) NOT for: General JS/TS (use code-reviewer), deep audit (use gas-quality-check), HTML patterns (use gas-ui-review)
code-audit-readonly
by Jpkovas
Execute a complete, deterministic, read-only repository audit and produce a single improvements.md action plan with traceable findings (file + lines), severity, category, impact, and high-level fixes. Use when users ask for full code audits, security/performance/architecture reviews, file-by-file analysis, or technical debt mapping without modifying project files.
react-anti-patterns
by joacod
Introduce React anti-patterns and common mistakes into existing React codebases for training, review, or teaching. Use when asked to intentionally degrade React performance or code quality while keeping apps functional, or to generate anti-pattern examples for junior developer education.
using-superpowers
by Crumbgrabber
Use when starting any conversation - establishes mandatory workflows
ai-review-validator
by mkdir700
Autonomously validate and execute AI Review suggestions from PR comments. Use when users provide AI Review comments (from GitHub Copilot, CodeRabbit, etc.) that suggest code changes, API migrations, or fixes. The skill verifies suggestions against official docs, tests compilation, calculates confidence scores, and auto-applies changes when verified. Triggers on phrases like "verify this AI Review", "apply this suggestion", "validate AI Review comment", or when users paste AI Review URLs/content.
baseline-security-audit
by enigmatry
Ensures baseline security practices are followed in the project. Use this when asked to perform a security audit on the codebase. Automatically creates Jira stories for each security finding.
gas-review
by whichguy
Unified GAS code review - runs BOTH gas-code-review AND gas-ui-review. ALWAYS PREFER THIS over gas-code-review or gas-ui-review individually. This agent provides cross-file analysis and parallel execution. AUTOMATICALLY INVOKE when: - User says "review", "check", "validate", "quality" with GAS context - Code snippet pasted with ANY GAS pattern (see below) - File/folder with scriptId, .gs files, or .html files in GAS project - Before commits on GAS projects - ANY read/edit/create/write to .gs or .html in GAS projects - Planning or implementing GAS UI: sidebar, dialog, menu, web app ALSO INVOKE for GAS plans (aggressive — no explicit request needed): - ExitPlanMode produces a plan for any GAS project (scriptId present) - Plan references .gs files, .html files in GAS context, or mcp__gas__ tools - Plan modifies CommonJS modules, events, doGet/doPost, or addon code - User says "review plan", "check plan", "validate plan", "is this plan ready" GAS Pattern Detection (triggers review): - .gs code: _main, defineModule, require(), module.exports, events, global - .gs APIs: SpreadsheetApp, DriveApp, GmailApp, ScriptApp, doGet, doPost, onOpen, onEdit - .html code: HtmlService, <?=, <?!=, google.script.run, createGasServer, exec_api - .html patterns: createTemplateFromFile, setXFrameOptionsMode, IFRAME embedding GAS UI/UX topics (with GAS context): - sidebar, dialog, modal, toast, menu, form in GAS projects - Google Picker, file upload, web app deployment - /exec vs /dev URLs, ContentService, CORS NOT for: General JS/TS (use code-reviewer), non-GAS HTML (use standard review)
Security Setup Skill
by hitoshura25
Create runbook for handling vulnerabilities
review-plan
by whichguy
Universal plan review: 3 layers (general quality, code change quality, ecosystem specialization). Invokes gas-plan for GAS plans or node-plan for Node.js/TypeScript plans, conditionally based on detected patterns. AUTOMATICALLY INVOKE when: - MANDATORY_PRE_EXIT_PLAN directive applies (before ExitPlanMode) - User says "review plan", "check plan", "plan ready?" - Any plan file needs review (GAS or non-GAS) NOT for: Code review of existing files (use /gas-review or /review-fix)
trae-skill-writer
by learnwy
"Create Trae IDE skills (SKILL.md files) for reusable AI capabilities. Use when user wants to: create a skill, make a reusable workflow, automate repetitive tasks, turn a conversation into a skill, or encapsulate a process for AI to follow. Triggers on: '创建 skill', 'write a SKILL.md', 'make this reusable', '.trae/skills/', 'I keep doing the same thing every time'. Do NOT use for rules (use trae-rules-writer) or agents (use trae-agent-writer)."
pipeline
by jwilger
Autonomous build-phase orchestrator. Manages slice queue, TDD pair dispatch, full-team code review, mutation testing, CI integration, and auto-merge with quality gates. Replaces manual coordinator overhead during build phase. Activate when running factory mode with ensemble-team.
brief-compliance
by jet52
Triggers when a user uploads a legal brief PDF for compliance review against the North Dakota Rules of Appellate Procedure. Analyzes the brief and produces an HTML compliance report with a recommended action (Accept, Correction Letter, or Reject).
cr-pr
by ThrownLemon
PR review comment management. Use when user wants to view or address PR review comments from any source.
verification-before-completion
by Crumbgrabber
Use when about to claim work is complete, fixed, or passing, before committing
agent-worker
by lidessen
Create and manage AI agent sessions with multiple backends (SDK, Claude CLI, Codex, Cursor). Also supports multi-agent workflows with shared context, @mention coordination, and collaborative voting. Use for "start agent session", "create worker", "run agent", "multi-agent workflow", "agent collaboration", "test with tools", or when orchestrating AI conversations programmatically.
ensemble-team
by jwilger
Set up a full AI ensemble/mob programming team for any software project. Creates team member profiles (.team/), coordinator instructions (.team/coordinator-instructions.md), project owner constraints (PROJECT.md), team conventions (AGENTS.md), architectural decisions (docs/ARCHITECTURE.md), domain glossary, and supporting docs. Use when: (1) starting a new project and wanting a full expert agent team, (2) the user asks to "set up a team", "create a mob team", "set up ensemble programming", or "create agent profiles", (3) converting an existing project to the driver-reviewer mob model, (4) the user wants AI agents to work as a coordinated product team with retrospectives and consensus-based decisions.