skills.rest
zytakeshi
zytakeshiCOMMUNITY
Explore all skills by this author →
GitHub

create-pr

Automate the full GitHub pull request lifecycle from commits to merge.

1|1|Updated Mar 21, 2026
Search Tags:#automation#git#workflow#codex#ci-cd#code-review#pull-request
One-click install
npx skills add https://github.com/zytakeshi/admin-skills --skill create-pr-zytakeshi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/zytakeshi/admin-skills/tree/main/skills/create-pr
Command: npx skills add https://github.com/zytakeshi/admin-skills --skill create-pr-zytakeshi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate the PR lifecycle from local changes to a GitHub pull request, including commit messaging, branch handling, Codex review, and merge readiness.

Core Features & Use Cases

  • Automates commit preparation and message drafting, with selective staging of changes.
  • Creates and pushes a feature branch, opens a PR with a structured body, and tracks Codex review.
  • Applies Codex-provided feedback across rounds, and merges when approved, or loops back for fixes.
  • Useful for teams seeking consistent PR processes and faster code delivery.

Quick Start

Create a PR from your current uncommitted changes and let this skill manage the full lifecycle.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate a pull request from uncommitted git changes to merge?▼

Automating a pull request from uncommitted changes is handled end-to-end by preparing commits, pushing a feature branch, opening a PR, tracking Codex review, and merging when approved. This ensures a consistent code delivery workflow.

Can I automatically apply Codex review feedback to my pull request?▼

Yes, Codex review feedback can be applied automatically across multiple rounds. The process loops back to apply fixes based on the review and proceeds to the final merge only when the feedback is fully resolved and approved.

How does this PR workflow handle sensitive files and git remotes?▼

The PR workflow enforces safety by excluding sensitive files from commits and ensuring the correct git remotes are used. It also requires explicit user confirmation before executing the final merge to prevent unintended repository changes.

What is the best way to manage selective staging before creating a feature branch?▼

The best way to manage selective staging is through automated commit preparation that drafts commit messages and stages specific changes. This targeted staging happens before creating and pushing the feature branch to open the pull request.

Does creating a PR with Codex require manual confirmation before merging?▼

Yes, creating a PR with Codex requires explicit user confirmation before the final merge. This safety check ensures you maintain control over the repository even while automating the commit preparation, branch pushing, and review tracking processes.

Related Skills

Explore More Software Engineering Skills→
zangxin75zangxin75

git-summary

Generate a Git repository summary with branch, status, commits, and remotes.

Community
Basic
vm0-aivm0-ai
76

pushinator

Send push notifications to mobile devices via the Pushinator API.

Official
Intermediate
Cogni-AI-OUCogni-AI-OU

pre-commit

Automate pre-commit checks for formatting, linting, and security on staged files.

Official
Advanced
zli5460zli5460
2

codex

Automates coding tasks, PR reviews, and issue fixes via Codex CLI in git repositories.

Community
Intermediate