Community PR Review and Merge

Community PRs go through a fixed quality checklist before merge. For trusted contributors (level99 has 7+ merged PRs), the maintainer commits fixes directly to the contributor's fork branch rather than requesting round-trip revisions — this preserves attribution while eliminating latency. An exception exists for first-time contributors who are historically unresponsive: when the fix is trivial (ruff format, simple doc change), apply fork-edit rather than request changes. This skill documents the full workflow from first look to merge, including technical validation for PRs that touch UniFi API tool implementations.

Prerequisites

• PR is open and CI workflow state is understood (see Step 0b for first-time contributor gotcha)
• You have push access to the contributor's fork (needed for the fork-edit model)
• AGENTS.md is current — it is the canonical source for hard bans
• For first-time contributors: check prior PR history to assess responsiveness (72+ hour silence threshold for fork-edit exception eligibility)
• For PRs touching tool implementations or API handlers: a live UniFi controller must be reachable to run smoke tests
• Makefile three-layer generation pipeline: make generate regenerates committed artifacts, make check-generated checks for drift, make pre-commit runs the full chain (format → generate → lint → test → drift checks). Run make pre-commit before opening any PR that modifies generated artifacts.