pr-review-as-liabadi

Analyze pull requests for Azure deployment, orchestration, and observability feedback.

126|8|Updated May 5, 2023
One-click install
npx skills add https://github.com/MoaidHathot/Neovim-Moaid --skill pr-review-as-liabadi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review-as-liabadi
Source: https://github.com/MoaidHathot/Neovim-Moaid/tree/main/config/Orchestra/Workspace/orchestrations/PullRequests/Personas/liabadi/Skills/persona-liabadi
Command: npx skills add https://github.com/MoaidHathot/Neovim-Moaid --skill pr-review-as-liabadi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a Liabadi-focused PR review perspective, covering Resource Providers, RPAAS, UserRP ARM, Azure deployment and RP semantics, orchestration correctness, and observability.

Core Features & Use Cases

  • Apply Liabadi's lens to PR reviews involving Azure deployments, EV2, Bicep, RP registrations, namespace configurations, and rollout steps.
  • Evaluate Durable Task / orchestration flows, asynchronous operations, LRO behavior, and status transitions.
  • Inspect ARM/RP API semantics and dual-namespace considerations, ensuring compatibility with live resources and proper controller boundaries.

Quick Start

Review the PR with Liabadi's Azure deployment and orchestration perspective.

Frequently Asked Questions about pr-review-as-liabadi

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

FAQPage Schema
How do I review Azure Bicep and ARM pull requests for correct RP semantics and dual-namespace handling?

Reviewing Azure Bicep and ARM pull requests for RP semantics involves analyzing resource provider API boundaries, dual-namespace compatibility, and controller constraints to ensure proper deployment compatibility and operability.

What does orchestration correctness evaluation cover for Azure Durable Task and LRO pull requests?

Orchestration correctness evaluation for Azure Durable Task covers asynchronous operations, Long-Running Operation (LRO) behavior, and status transitions to verify proper flow execution and rollback readiness.

How do I check Azure EV2 rollout steps and RP registrations for observability and logging before deployment?

Checking Azure EV2 rollout steps and RP registrations requires inspecting orchestration configurations, validating resource provider boundaries, and ensuring clear guidance on logging, diagnostics, and rollback readiness.

Does this PR review approach work for test-infrastructure changes and Azure platform backend deployments?

This PR review approach works for backend, cloud platform, deployment, RP registration, and test-infrastructure changes where evaluating orchestration correctness, ARM/RP API semantics, and observability clarifies proper boundaries.

When should I not use a Liabadi-style Azure deployment review for my pull request?

You should avoid using a Liabadi-style Azure deployment review for pull requests that do not involve resource provider registrations, ARM semantics, orchestration flows, or observability and logging configurations.

Can I use this review perspective to validate namespace configurations and controller boundaries in Azure deployments?

You can use this review perspective to validate namespace configurations, dual-namespace considerations, and controller boundaries by inspecting ARM/RP API semantics to ensure compatibility with live resources.