af-review-ui

Audit Airflow UI frontend code for consistency and best practices.

1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/guan404ming/gmccc --skill af-review-ui
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: af-review-ui
Source: https://github.com/guan404ming/gmccc/tree/main/skills/airflow/af-review-ui
Command: npx skills add https://github.com/guan404ming/gmccc --skill af-review-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit Airflow UI codebase to ensure consistency with project conventions, identify deviations, and improve maintainability.

Core Features & Use Cases

  • Audit frontend UI components for reuse from src/components/ui/
  • Enforce types from openapi-gen and readonly props; ensure undefined instead of null
  • Provide PR-ready review notes and inline suggestions for changes

Quick Start

Review the Airflow UI changes in your PR using the built-in checklist and generate inline review suggestions.

Frequently Asked Questions about af-review-ui

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

FAQPage Schema
How do I review Airflow UI code for consistency in a PR?▼

Review Airflow UI code by auditing component usage from src/components/ui/, enforcing openapi-gen types, validating readonly props, and ensuring null handling uses undefined. Generate inline PR-ready review notes and suggestions.

What are the best practices for Airflow frontend component reuse?▼

Airflow frontend best practices mandate reusing UI components from src/components/ui/, enforcing readonly props, aligning with openapi-gen types, and replacing null with undefined to ensure type integrity and code readability.

Can I use standard lint rules to audit Airflow UI changes locally?▼

Yes, you can audit local Airflow UI changes using standard lint rules alongside component validation checks. This ensures your frontend code adheres to project conventions, openapi-gen types, and readability standards before creating a PR.

Does Airflow UI frontend code require undefined instead of null for props?▼

Yes, Airflow UI frontend code requires using undefined instead of null for props. Auditing enforces correct null handling and readonly prop integrity to maintain consistency with openapi-gen types and project conventions.

How to check if my PR violates Airflow UI component conventions?▼

Check PR violations by auditing frontend changes against a built-in checklist for reusable component validation, openapi-gen type alignment, and lint rules to generate inline review suggestions for any deviations.