create-pr

Name: create-pr
Availability: InStock
Author: t-hasuike

Plan code changes from impact analysis and create pull requests from approved proposals.

Updated Mar 11, 2026

Search Tags:#automation #git #end-to-end #pull-request #code-change #human-checkpoint

Ready to run

npx skills add https://github.com/t-hasuike/CLysis --skill create-pr-t-hasuike

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/t-hasuike/CLysis/tree/main/legacy-execution/skills/create-pr
Command: npx skills add https://github.com/t-hasuike/CLysis --skill create-pr-t-hasuike

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage end-to-end code changes with built-in governance, separating planning from execution to ensure human judgment gates are honored.

Core Features & Use Cases

Plan phase: generate change proposals from impact analysis reports
Exec phase: create a branch, apply changes, commit, push, and open a PR from approved proposals
Human checkpoints: enforced approval between phases to prevent unvetted changes
Use case: teams performing large refactors or policy-driven updates requiring auditable change histories

Quick Start

Run the plan phase with your impact analysis report to generate a proposal, then review and approve it before executing the PR creation.

Frequently Asked Questions about create-pr

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

FAQPage Schema

How do I automate pull request creation while keeping human approval for code changes?▼

Automated pull request creation with human approval separates planning from execution by generating proposals from impact analysis, enforcing a manual review checkpoint, then creating branches and opening PRs for approved changes.

What is the best way to manage large-scale refactors with governance and human checkpoints?▼

Managing large-scale refactors with governance requires separating planning from execution, generating change proposals from impact analysis reports, and enforcing human approval before creating branches and opening pull requests.

How do I generate a change proposal from an impact analysis report for a git pull request?▼

To generate a change proposal from an impact analysis report, run the plan phase to coordinate proposed code changes, which are subsequently reviewed and approved before execution via pull request creation.

Do I need valid GitHub access to execute approved change proposals and open a pull request?▼

Valid GitHub access for the target repository is required to execute approved change proposals, allowing the system to create a branch, apply changes, commit, push, and open a pull request.

Can I execute code modifications without an approved change proposal?▼

Executing code modifications requires an approved change proposal from the plan phase, ensuring human judgment gates are honored and preventing unvetted changes before creating a pull request.

What are the limitations of separating planning from execution for code changes?▼

Separating planning from execution requires an impact analysis report for the plan phase and an approved change proposal for the exec phase, meaning execution is blocked until manual review is completed.