create-pr

To turn dirty working-tree changes into a pull request, this Skill groups uncommitted files into coherent Conventional Commit units, creates a topic branch, pushes the commits, and opens a PR against main.

Yes, you can automatically enable auto-merge when creating a GitHub pull request. After grouping changes into commits and pushing to origin, the Skill opens the pull request and enables the auto-merge feature.

You group uncommitted files into conventional commit units by surveying staged, unstaged, and untracked changes, then sorting them into the smallest coherent logical groups for individual commits.

Yes, this pull request automation runs formatting and tests before the first commit. It applies workspace validation including linting, testing, and markdown checks to ensure you avoid opening a broken PR.

The best way to automate branching from a dirty repository is using a workflow that reads uncommitted changes, creates or reuses a topic branch, commits grouped units in order, and pushes to origin.

You should not use an automated tool to group local edits when your working tree contains changes that require complex manual staging or custom commit message formatting outside the Conventional Commits standard.