skills.rest
marcocpt
marcocptCOMMUNITY
Explore all skills by this author →
GitHub

github-pull

Commits local branch changes and merges them into develop via GitHub pull requests.

Updated Jun 11, 2026
Search Tags:#automation#git#pull request#github#cli#merge#swiftlint
One-click install
npx skills add https://github.com/marcocpt/trae_skills --skill github-pull-marcocpt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-pull
Source: https://github.com/marcocpt/trae_skills/tree/main/github-pull
Command: npx skills add https://github.com/marcocpt/trae_skills --skill github-pull-marcocpt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually pushing local changes, running lint checks, and managing pull requests to merge into the develop branch is repetitive and error-prone. This Skill automates the entire flow from local commit to merged pull request. ## Core Features & Use Cases - Automated Commit & Push: Fetches the latest version of the local branch and commits pending local modifications using the GitHub CLI. - SwiftLint Validation: Runs SwiftLint checks and fixes issues before creating the pull request. - Pull Request Management: Checks for an existing pull request, creates a new one if none exists, updates it otherwise, and merges into the develop branch. - Use Case: An iOS developer finishes a feature on a local branch and wants it merged into develop. The Skill commits the work, lints the Swift code, opens or updates the PR, and completes the merge. ## Quick Start Commit my current branch changes, run SwiftLint, and merge them into develop through a GitHub pull request.

Frequently Asked Questions about github-pull

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

FAQPage Schema
How do I merge a local branch into develop using GitHub CLI?▼

Use the GitHub CLI to commit local changes, push the branch, then create a pull request targeting develop with gh pr create. If a pull request already exists for the branch, update it instead and merge with gh pr merge.

How to run SwiftLint before creating a pull request?▼

Run SwiftLint on the local branch after committing changes and fix any reported violations before pushing. This ensures the pull request only contains code that passes lint checks.

Does GitHub CLI detect existing pull requests for a branch?▼

Yes, the GitHub CLI can check whether a pull request already exists for the current branch. The workflow creates a new pull request when none exists and updates the existing one otherwise.

What happens if SwiftLint finds errors during the workflow?▼

SwiftLint issues are checked and fixed before the pull request is created or updated. Code that fails lint checks should be corrected locally first so the merged branch stays clean.

Can this workflow merge branches other than develop?▼

The workflow is defined to merge into the develop branch specifically. Targeting a different base branch would require adjusting the pull request creation step accordingly.

Related Skills

Explore More Software Engineering Skills→
aberrantCodeaberrantCode
1

publish-github

Publish local projects to GitHub with gitleaks hooks and protected branches.

Community
Advanced
mikkeymoomikkeymoo
1

mm-ship

Automate test runs, PR creation, merging, and post-ship follow-ups.

Community
Intermediate
HomericIntelligenceHomericIntelligence
18

verify-pr-ready

Validate GitHub Pull Requests for CI status, approvals, and merge conflicts.

Official
Intermediate
VirtusLabVirtusLab
1.1k

git-machete

Manage git branch chains and automate rebases and merges.

Official
Advanced