pr

Create pull requests from dev to main with version bumps and auto-merge.

26|2|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/Llloooggg/LetsFLUTssh --skill pr-llloooggg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/Llloooggg/LetsFLUTssh/tree/main/.claude/skills/pr
Command: npx skills add https://github.com/Llloooggg/LetsFLUTssh --skill pr-llloooggg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual PR workflows slow down development: merging from dev to main, syncing branches, and bumping versions are repetitive and error-prone.

Core Features & Use Cases

  • Automates the end-to-end PR workflow from dev to main, including version bumps and an auto-merge option.
  • Syncs branches to ensure dev and main are aligned before PR creation.
  • Applies to multi-branch repositories where release-ready changes must pass through a formal PR process.

Quick Start

Create a PR from dev to main following the project's merge flow.

Frequently Asked Questions about pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate pull requests from dev to main with a version bump?▼

To automate pull requests from dev to main with a version bump, this Skill verifies a clean working tree, syncs branches, runs your project's bump script, and creates an auto-merging PR automatically.

What is the best way to sync dev and main branches before creating a pull request?▼

The best way to sync dev and main branches before a pull request is using an automated workflow that checks for a clean working tree and aligns the branches to prevent manual sync errors.

Can I automatically merge pull requests in a multi-branch git workflow?▼

Yes, you can automatically merge pull requests in a multi-branch git workflow by configuring an automated process that creates the PR and applies auto-merge after syncing branches.

How does an automated version bump work before creating a pull request?▼

An automated version bump before a pull request works by executing the project's designated bump script after verifying a clean working tree and syncing the dev and main branches.

Why do my manual PR workflows from dev to main fail during branch syncing?▼

Manual PR workflows from dev to main often fail during branch syncing due to uncommitted changes or misaligned branches, which automated verification of a clean working tree prevents.

Do I need a clean working tree to automate git pull requests?▼

Yes, you need a clean working tree to automate git pull requests because the workflow checks for uncommitted changes before syncing branches and executing the version bump script.