connector-code-quality-review

Review connector integration changes for UCS architecture, security, and conventions.

Updated Dec 11, 2025
One-click install
npx skills add https://github.com/maverox/claude-plugins --skill connector-code-quality-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: connector-code-quality-review
Source: https://github.com/maverox/claude-plugins/tree/main/plugins/connector-integration-suite/skills/connector-code-quality-review
Command: npx skills add https://github.com/maverox/claude-plugins --skill connector-code-quality-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the detection of UCS architecture violations, security risks, and project-convention gaps in connector implementation changes.

Core Features & Use Cases

  • Automated quality checks on connector changes across PRs, with auto-activation for common requests.
  • Issue-based feedback that highlights Critical, Warning, and Suggestion items with actionable guidance.
  • Usage scenarios include PR review, targeted file analysis, and inline diff examination for quick remediation.

Quick Start

Run a PR-quality review on a connector PR to generate a structured feedback report.

Frequently Asked Questions about connector-code-quality-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code review for connector PRs?

Automated connector PR review scans integration changes for UCS architecture conformance, security risks, and project conventions. It processes PR diffs and file contents to return a YAML-formatted report categorizing issues as critical, warning, or suggestion.

How does static analysis detect UCS architecture violations in connectors?

Static analysis for connector code validates integration changes against UCS architecture conformance and security best practices. It examines PR file lists, head commits, and new file contents to generate line-level pointers for precise issue identification.

Can I run a targeted file analysis on specific connector changes?

Targeted file analysis allows you to review specific connector files or inline diffs for UCS conformance. The process validates line-level pointers in the new file contents and generates a structured YAML report with actionable remediation guidance.

What security best practices are checked during connector code quality scans?

Security best practices checks during connector quality scans identify vulnerabilities and project-convention gaps in integration changes. The scan categorizes detected security issues into critical, warning, and suggestion levels within a structured YAML report.

What inputs are required to generate a structured PR review report?

Generating a structured PR review report requires access to the PR file list, the PR head commit, and the new file contents. These inputs enable line-level validation of connector changes and produce a YAML-formatted issue report.

What is the best way to review inline diffs for connector integration changes?

The best way to review inline diffs is to apply automated quality checks that validate UCS architecture conformance and security practices. This returns issue-based feedback highlighting critical items with actionable guidance for quick remediation.