Skill UI

This skill details how to configure CodeRabbit review behavior using a `.coderabbit.yaml` file placed on base branches. It enables setting tailored code quality gates across the development lifecycle, allowing for relaxed reviews on feature branches and highly stringent, security-focused checks for production or release environments, ensuring quality matches risk.

Monitor the effectiveness and adoption of AI code reviews using CodeRabbit. This skill calculates critical metrics including review coverage percentage, time-to-first-review, and comment acceptance rates. It is ideal for building organizational dashboards to maintain high code quality and optimize development workflows.

This comprehensive checklist guides users through the process of elevating CodeRabbit from an optional AI review tool to a mandatory merge gate in a production environment. It covers configuration auditing, technical validation (YAML syntax, review coverage), team onboarding, and setting up branch protection rules to ensure a smooth transition to required status.

This guide helps users manage their CodeRabbit setup, covering plan upgrades (e.g., Free to Pro/Enterprise) and migrating configuration files. It details how to update the .coderabbit.yaml schema to adopt the latest features, advanced workflows, and best practices for enhanced code review automation.

Analyzes namespaces to spot root-level orphaned classes, highlights hierarchy violations, and produces flattening or refactoring plans that keep components at leaf-level directories.

Automates Composio Search workflows through Rube MCP by discovering the latest tool schemas first, validating connections, and executing schema-compliant multi-tool calls for reliable search operations.

This skill automatically generates comprehensive and highly structured Pull Request (PR) descriptions directly from Git diffs. It goes beyond simple summaries by automatically adding detailed change categories (e.g., source, test, config), security risk assessments, and required review checklists based on the modified file types. Use this when submitting complex code changes or when the diff is large and requires explicit structure for thorough review.

Automates cross-browser compatibility verification by orchestrating BrowserStack, Selenium Grid, or Playwright runs across Chrome, Firefox, Safari, and Edge, capturing screenshots/logs and producing a report when requested via `/browser-test`/`/bt` to confirm web app behavior across devices.

This skill guides the execution of development tasks defined in a structured implementation plan, strictly following the Test-Driven Development (TDD) workflow. It manages the entire development lifecycle, including pre-flight checks, context loading, task identification, writing failing tests, implementing minimal code, refactoring, committing changes, and performing phase-wise verification. Ideal for managing complex, structured software development projects.

This skill provides comprehensive management for the entire track lifecycle within a Conductor system. It allows users to perform critical operations such as archiving, restoring, deleting, renaming tracks, and cleaning up orphaned artifacts. Use it when managing track status across active, completed, or archived states to ensure data integrity and system organization.

This skill is designed to configure a Rails project workspace to function correctly within Conductor, a platform for parallel coding agents. It sets up the necessary scaffolding, including `conductor.json`, executable setup scripts, and server scripts. Additionally, it updates critical Rails configuration files (such as Sidekiq, Cable, and development environment settings) to ensure proper environment variable handling, Redis isolation, and port management for reliable parallel agent execution.

This skill provides a comprehensive, actionable overview of the Conductor project's status. It aggregates information from project plans, active tracks, and detailed specifications to display overall progress, identify next critical tasks, and flag potential blockers. Use it when you need a high-level dashboard view of project health and required actions.