How does the skill handle duplicate pull requests?

The skill is idempotent; it checks for existing PRs via the GitHub API before attempting to create a new one, providing the existing URL instead of creating a duplicate.

What happens if my fork has a different name than the upstream repository?

The skill uses smart detection via the GitHub API to identify your fork regardless of its name and correctly configures the origin and upstream remotes.

Is DCO sign-off supported for commits?

Yes, all commits generated by the skill automatically include the -s flag to ensure Developer Certificate of Origin (DCO) compliance for open-source contributions.

Does this skill require the GitHub CLI?

Yes, you must have the GitHub CLI (gh) installed and authenticated on your machine for the skill to perform forks and create pull requests.

Can I use this with an existing local repository?

Absolutely. You can specify the current directory as the workspace to automate the PR process for a repository you already have cloned locally.

Git PR Automator

Name: Git PR Automator
Author: yanmxa

byyanmxa

•

Deployment & DevOps

Automates the end-to-end process of forking, branching, committing, and submitting pull requests to GitHub repositories.

The Git PR Automator is designed to eliminate the repetitive boilerplate of contributing to software projects by streamlining the entire pull request lifecycle. It handles everything from smart fork detection and high-speed shallow cloning to managing upstream remotes and ensuring DCO-compliant commits. By automating the technical overhead of git workflows, it allows developers to focus entirely on code changes while maintaining a clean, idempotent submission process that prevents duplicate PRs.