pr-pipeline-impl

You can automate PR creation and local verification by invoking the pipeline implementation skill with an issue number, which drafts pull requests, runs local pytest checks, and records merge-gate evidence for GitHub pipelines.

A merge gate in automated code review pipelines is a strict compliance contract that requires recorded evidence of local verification and architectural compliance before a PR is handed off for final bot review.

Yes, the PR pipeline implementation process works with uv and ruff environments, utilizing them as core dependencies to manage project environments and enforce code formatting standards during the automated implementation phase.

Multi-PR lanes during automated registry research tasks are managed by the pipeline skill, which handles planning, claiming, implementation, and gate recording while deferring final bot review to the lane-runner.

Automated PR pipeline implementation requires untrusted-data boundaries to enforce strict safety and architectural compliance, ensuring that potentially malicious registry data is isolated and handled safely during the implementation phase.