pr

This skill streamlines the software development lifecycle by automating the creation of draft pull requests on GitHub. Designed for developers working within the Windmill ecosystem, it ensures that all code contributions are high-quality, properly documented, and reviewed before reaching the main branch. It acts as a safety guard, integrating local review processes and verifying branch state before interacting with the remote repository. By enforcing conventional commit titles and a standardized PR body template, it minimizes human error and reduces the cognitive load associated with preparing PRs.

• Automatically analyzes branch changes and commits since diverging from main to provide an accurate summary.

• Enforces conventional commit formatting for PR titles (feat, fix, refactor, docs, chore, perf) to maintain clean git history.

• Mandates a local-review step to prevent syntax errors, compilation failures, or compliance violations before PR submission.

• Provides built-in support for enterprise companion PRs, automatically handling symlinked EE files and multi-repository synchronization.

• Utilizes the GitHub CLI (gh) to generate structured PR bodies including summaries, change logs, and test plans.

• Requires explicit test plans to ensure every change can be verified by maintainers.

• Always run local-review before executing the PR creation command to identify high-signal issues.

• Ensure all commits are pushed to the remote repository before initiating the process.

• Use the [ee] prefix in the PR title when modifying enterprise-specific (*_ee.rs) files.

• The tool expects standard git workflows; confirm upstream branches are tracked correctly using git rev-parse.

• The generated PR body supports markdown, allowing for detailed descriptions of implementation details and validation steps.

• Target audience: Software engineers contributing to Windmill or similar complex codebases requiring strict PR governance and high code quality standards.