create-zakura-pr

Create draft pull requests for the Zakura repository using the GitHub CLI.

42|10|Updated Jun 12, 2026
One-click install
npx skills add https://github.com/zakura-core/zakura --skill create-zakura-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-zakura-pr
Source: https://github.com/zakura-core/zakura/tree/main/.agents/skills/create-zakura-pr
Command: npx skills add https://github.com/zakura-core/zakura --skill create-zakura-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the friction and overhead of manual pull request creation by enforcing a standardized, draft-first workflow that ensures early visibility and consistent quality for Zakura node development.

Core Features & Use Cases

  • Draft-First Automation: Automatically opens pull requests in draft mode to trigger CI pipelines immediately while local verification continues.
  • Risk-Based Verification: Provides a structured framework for determining when to run intensive local tests versus relying on automated CI checks.
  • Use Case: When you have finished a feature branch for a consensus optimization, use this skill to open a draft PR, run the required Markdown linting, and prepare the branch for review without manually navigating the GitHub CLI.

Quick Start

Use the create-zakura-pr skill to open a new draft pull request for the current branch with the standard template.

Frequently Asked Questions about create-zakura-pr

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

FAQPage Schema
How do I automate pull request creation with a draft-first workflow on GitHub?

A draft-first pull request workflow automatically opens PRs in draft mode via the GitHub CLI, triggering CI pipelines immediately while local verification and branch diff reviews continue before marking the PR ready for review.

What is risk-proportional testing when managing GitHub pull requests?

Risk-proportional testing provides a structured framework for determining when to run intensive local tests versus relying on automated CI checks, balancing verification depth with the perceived risk of the branch changes.

Do I need the GitHub CLI installed to automate draft pull requests?

Yes, you need the GitHub CLI installed. The automation requires the GitHub CLI to execute PR creation, manage branch status updates, and integrate IDE diagnostics within the repository environment.

How to run branch diff reviews and IDE diagnostics before opening a GitHub pull request?

To run branch diff reviews and IDE diagnostics before opening a GitHub pull request, use an automation skill that facilitates these checks locally while simultaneously opening a draft PR to trigger remote CI pipelines.

What's the best way to enforce consistent development workflows for pull requests?

The best way to enforce consistent development workflows for pull requests is adopting a draft-first automation methodology that standardizes branch diff reviews, IDE diagnostics, and risk-proportional testing across all feature branches.

Why open a draft pull request before local verification is finished?

Opening a draft pull request before local verification is finished provides early visibility and triggers CI pipelines immediately, allowing local checks and remote automated testing to run concurrently to reduce overall cycle time.