# PR

Open a draft pull request on GitHub and drive CI review rounds until it is ready.

- Repository: https://github.com/windmill-labs/windmill (18352 stars)
- Category: Git and review
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add windmill-labs/windmill --skill pr -g -a claude-code -y`
Codex: `npx skills add windmill-labs/windmill --skill pr -g -a codex -y`
Cursor: `npx skills add windmill-labs/windmill --skill pr -g -a cursor -y`
Gemini CLI: `npx skills add windmill-labs/windmill --skill pr -g -a gemini-cli -y`

## Description

Open a draft pull request on GitHub and drive CI review rounds until it is ready. MUST use when you want to create/open a PR.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Pull Request Skill

Create a draft pull request with a clear title and explicit description of changes, then drive it through CI review rounds to ready.

## Instructions

1. **Analyze branch changes**: Understand all commits since diverging from main
2. **Push to remote**: Ensure all commits are pushed
3. **Create draft PR**: Always open as draft for review before merging
4. **Drive review rounds**: trigger CI reviews on the draft and only flip to ready once every verdict is a go (see "Review rounds" below)

## PR Title Format

Follow conventional commit format for the PR title:
```
<type>: <description>
```

### Types
- `feat`: New feature or capability
- `fix`: Bug fix
- `refactor`: Code restructuring
- `docs`: Documentation changes
- `chore`: Maintenance tasks
- `perf`: Performance improvements

### Title Rules
- Keep under 70 characters
- Use lowercase, imperative mood
- No period at the end
- If `*_ee.rs` files were modified, prefix with `[ee]`: `[ee] <type>: <description>`

## PR Body Format

The body MUST be explicit about what changed. Structure:

```markdown
## Summary
<Clear description of what this PR does and why>

## Changes
- <Specific change 1>
- <Specific change 2>
- <Specific change 3>

## Test plan
- [ ] <How to verify change 1>
- [ ] <How to verify change 2>
```

The harness/tooling that invoked the skill may add its own attribution trailer; the skill itself does not prescribe one.

## Screenshots (required for frontend changes)

If `git diff main...HEAD --name-only` matches `^frontend/`, the PR body **must** include
screenshots of the affected UI. Skip only when there is no visible UI effect (types,
tests, build config), and say so in the body.

The rest: https://github.com/windmill-labs/windmill/blob/HEAD/.agents/skills/pr/SKILL.md