i-pr

Automates pull request creation by resolving worktrees, validating changes, and pushing commits.

12|1|Updated Dec 27, 2025
One-click install
npx skills add https://github.com/apokamo/kaji --skill i-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i-pr
Source: https://github.com/apokamo/kaji/tree/main/.claude/skills/i-pr
Command: npx skills add https://github.com/apokamo/kaji --skill i-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

workflow 共通の PR 作成を担当するスキルで、worktree の解決、未コミット変更の確認、Push、kaji pr create の処理を限定して実行します。

Core Features & Use Cases

  • Worktree resolution & pre-PR checks: Worktree の絶対パス取得と未コミット変更の検出を行います。
  • PR creation as a focused step: PR 作成のみを実行し、PR の本文更新やマージなどは他のステップに任せます。
  • Issue workflow integration: IssueStart 以降の PR 作成を連携させ、PR 情報をワークフロー全体で追跡できるようにします。

Quick Start

Run the i-pr skill after starting an issue to create and link a PR for the current worktree.

Frequently Asked Questions about i-pr

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

FAQPage Schema
How do I automate pull request creation from a git worktree?

Automating pull request creation from a worktree involves resolving the absolute path, validating uncommitted changes, and pushing commits before executing the PR creation command. This Skill coordinates those steps and outputs a consistent PR URL.

What steps are needed to create a PR with uncommitted changes in a worktree?

Creating a PR with uncommitted changes requires detecting those changes first, resolving the worktree path, and pushing commits. This Skill enforces those pre-PR checks and executes the focused PR creation step, returning a success or abort verdict.

Can I use this to update the PR body or merge a pull request after creation?

Updating the PR body or merging a pull request after creation is not supported here. This Skill performs only the focused PR creation step and optional post-PR updates to issue bodies, leaving other actions to separate workflow steps.

Does pull request automation work with both GitHub and local git providers?

Pull request automation supports both GitHub and local modes. It coordinates provider checks through PR creation, enforces output guardrails, and expects a consistent PR URL format regardless of the provider.

How do I link an issue workflow to a newly created pull request?

Linking an issue workflow to a newly created pull request is done by running this Skill after starting an issue. It creates and links the PR for the current worktree, optionally updating the issue body with PR information for tracking.

Why does my automated PR creation abort without creating a pull request?

Automated PR creation aborts when pre-PR guardrails fail, such as detecting unresolved uncommitted changes or missing worktree paths. The Skill reports an explicit abort verdict rather than proceeding with an invalid state.