auto-create-pr

Automates GitHub Pull Request creation from task plans with progress tracking.

Updated May 31, 2026

Search Tags:#ci/cd #code review #task management #github #pr automation

Ready to run

npx skills add https://github.com/zizzfizzix/agentic-engineering-framework --skill auto-create-pr-zizzfizzix

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: auto-create-pr
Source: https://github.com/zizzfizzix/agentic-engineering-framework/tree/main/core/ai/skills/auto-create-pr
Command: npx skills add https://github.com/zizzfizzix/agentic-engineering-framework --skill auto-create-pr-zizzfizzix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of creating GitHub Pull Requests (PRs) from tasks, eliminating manual steps and reducing the time to merge code changes.

Core Features & Use Cases

Task-to-PR Automation: Convert tasks into executable plans and create PRs against the default branch.
Progress Tracking: Maintain a progress checklist within the plan for resumable execution.
Use Case: Ideal for CI/CD pipelines, where automated tasks need to be converted into PRs with minimal human intervention.

Quick Start

Run the auto-create-pr skill with the task description 'Automate deployment of new features to production'.

Frequently Asked Questions about auto-create-pr

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

FAQPage Schema

How do I automate GitHub Pull Request creation from tasks in a CI/CD pipeline?▼

Automating GitHub PR creation from tasks involves converting task briefs into execution plans and using the GitHub API to generate PRs with normalized labels. This eliminates manual steps and streamlines software delivery within CI/CD workflows.

Can I track progress and resume execution for automated PR generation?▼

You can track progress and resume execution because the automation maintains a progress checklist within the execution plan. This allows resumable execution of automated tasks before the final GitHub Pull Request is created against the default branch.

Do I need the GitHub API to automate PR creation for autonomous tasks?▼

You need the GitHub API to automate PR creation because the process requires direct interaction with GitHub to generate pull requests. It also requires executing project validation commands to ensure code changes meet repository standards before merging.

What's the best way to convert autonomous tasks into executable plans with normalized labels?▼

The best way to convert autonomous tasks into executable plans with normalized labels is using an automation skill that processes task briefs and tracks pipeline execution. This approach ensures consistent PR labeling and reduces human intervention in software delivery.

Are there limitations when creating PRs against the default branch from automated tasks?▼

A limitation when creating PRs against the default branch is the strict requirement for successful project validation commands. If autonomous tasks fail execution or validation, the PR generation process halts to prevent introducing unverified code changes into the pipeline.