pr-make-suggestion-to-pr

Create separate suggestion PRs from unstaged edits, each based on the current PR branch. Use when: (1) User says 'suggestion to pr' or 'create suggestion PRs', (2) After /pr-make-suggestion-edit has left unstaged changes that need to be turned into separate PRs by topic.

6 stars

Best use case

pr-make-suggestion-to-pr is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Create separate suggestion PRs from unstaged edits, each based on the current PR branch. Use when: (1) User says 'suggestion to pr' or 'create suggestion PRs', (2) After /pr-make-suggestion-edit has left unstaged changes that need to be turned into separate PRs by topic.

Teams using pr-make-suggestion-to-pr should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/pr-make-suggestion-to-pr/SKILL.md --create-dirs "https://raw.githubusercontent.com/Takazudo/claude-resources/main/skills/pr-make-suggestion-to-pr/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/pr-make-suggestion-to-pr/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How pr-make-suggestion-to-pr Compares

Feature / Agentpr-make-suggestion-to-prStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Create separate suggestion PRs from unstaged edits, each based on the current PR branch. Use when: (1) User says 'suggestion to pr' or 'create suggestion PRs', (2) After /pr-make-suggestion-edit has left unstaged changes that need to be turned into separate PRs by topic.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# PR Make Suggestion To PR

Create separate pull requests for each suggestion topic from the unstaged changes, with each PR based on the current PR branch.

## Context

This command is typically used after `/pr-make-suggestion-edit` which leaves unstaged changes. These changes represent suggestions to improve the current PR, grouped by topic.

## Process

### Step 1: Analyze Unstaged Changes

1. Check current branch and PR
2. View all unstaged changes: `git status`, `git diff --stat`, `git diff`
3. Analyze the changes and determine logical groupings

### Step 2: Group Changes by Topic

Examples of topics:

- Formatting errors
- Type safety improvements
- Refactoring for better patterns
- Performance optimizations
- Accessibility improvements

Present the groupings to the user for confirmation.

### Step 3: Create Suggestion PRs

For **each topic**, create a separate PR:

1. **Create a new branch based on CURRENT branch (not base branch)**

   ```bash
   git checkout -b suggest/[descriptive-topic-name] $ORIGINAL_BRANCH
   ```

2. **Selectively stage only files for this topic**

3. **Create commit following project conventions**

   ```bash
   git commit -m "suggest: [clear description]"
   ```

4. **Push and create PR targeting the original PR branch**

   ```bash
   gh pr create --base $ORIGINAL_BRANCH --title "suggest: [title]"
   ```

5. **Return to original branch for next topic**

### Step 4: Verify and Report

List all created PRs and remaining unstaged changes.

## Important Rules

### Branch Strategy

- **Base suggestion PRs on the CURRENT PR branch** (not on main/master)
- Branch names should start with `suggest/`
- This creates a chain: main <- original-pr <- suggestion-pr

### Commit & PR Conventions

- **PR titles MUST start with `suggest: `**
- Follow project's commit message format
- Follow project's PR format

### Process

- One topic = One PR (don't mix unrelated changes)
- Stage only relevant files for each PR
- Test that changes still work (type check if applicable)
- Provide clear URLs to all created PRs

## Notes

- This command works with `/pr-make-suggestion-edit` as a pair
- Each suggestion PR is **independent and reviewable**
- The base PR maintainer can choose which suggestions to merge
- After merging suggestions, they become part of the base PR

Related Skills

pr-make-suggestion-edit

6
from Takazudo/claude-resources

Review current PR and make improvement edits without committing. Use when: (1) User says 'suggestion edit', 'suggest improvements', or 'review and edit', (2) User wants code quality improvements as unstaged edits for selective PR creation. Companion to /pr-make-suggestion-to-pr.

zudoesa-articlify

6
from Takazudo/claude-resources

Convert conversation context into an esa article via the zudoesa-writer subagent. ONLY invoke when the user explicitly asks — NEVER proactively propose. Triggers: 'write esa article', 'esa記事', 'esaに書いて', 'articlify for esa', or /zudoesa-articlify. Gathers context, creates a writing brief, delegates to the writer subagent.

zudoesa-apply-voice

6
from Takazudo/claude-resources

Apply Takazudo's esa writing voice and vocabulary rules to text. Use when: (1) User wants to write/rewrite text in Takazudo's esa style, (2) User says 'apply voice', 'esa voice', 'esa文体で', 'esa風に書いて', '文体を適用', (3) User provides text to transform to esa style. Reads writing-style.md and vocabulary-rule.md from takazudo-esa-writing repo and applies the rules.

zudocg-articlify

6
from Takazudo/claude-resources

Convert conversation context into a CodeGrid article via the zudocg-writer subagent. ONLY invoke when the user explicitly asks — NEVER proactively propose. Triggers: 'write codegrid article', 'CodeGrid記事', 'codegridに書いて', 'articlify for codegrid', or /zudocg-articlify. Gathers context, creates a writing brief, delegates to the writer subagent.

zudocg-apply-voice

6
from Takazudo/claude-resources

Apply Takazudo's CodeGrid writing voice and vocabulary rules to text. Use when: (1) User wants to write/rewrite text in Takazudo's CodeGrid style, (2) User says 'apply voice', 'codegrid voice', 'codegrid文体で', 'codegrid風に書いて', '文体を適用', (3) User provides text to transform to CodeGrid style. Reads writing-style.md and vocabulary-rule.md from takazudo-codegrid-writing repo and applies the rules.

zpaper-articlify

6
from Takazudo/claude-resources

Convert conversation context into a zpaper blog article via the zpaper-writer subagent. ONLY invoke when the user explicitly asks — NEVER proactively propose. Triggers: 'write zpaper article', 'zpaper記事', 'zpaperに書いて', 'articlify for zpaper', or /zpaper-articlify. Gathers context, creates a writing brief, delegates to the writer subagent.

zpaper-apply-voice

6
from Takazudo/claude-resources

Apply Takazudo's zpaper blog writing voice and vocabulary rules to text. Use when: (1) User wants to write/rewrite text in Takazudo's zpaper style, (2) User says 'apply voice', 'zpaper voice', 'zpaper文体で', 'zpaper風に書いて', 'ブログ文体を適用', (3) User provides text to transform to zpaper style. Reads writing-style.md and vocabulary-rule.md from the zpaper repo and applies the rules.

xlsx

6
from Takazudo/claude-resources

Spreadsheet creation, editing, and analysis. Use when working with .xlsx, .xlsm, .csv, .tsv files for: (1) Creating spreadsheets with formulas and formatting, (2) Reading or analyzing data, (3) Modifying existing spreadsheets while preserving formulas, (4) Data analysis and visualization, (5) Recalculating formulas.

x

6
from Takazudo/claude-resources

Facade for development workflows. Routes on two axes: plan-first vs implement-now (escalates to /big-plan -a when the request needs research / decomposition / has unclear scope — the appended -a makes the plan chain into implementation in-session), then single vs multi on the ready-to-build fast paths (/x-as-pr single-topic, /x-wt-teams multi-topic parallel). Use when: (1) User says '/x' followed by dev instructions, (2) User wants to start development without choosing the workflow skill, (3) User says 'dev', 'implement', or 'build' with a task. Default option: -v (verify-ui). Review-loop (-l) is opt-in — without -l the downstream skill runs a single /deep-review pass. Forwards -a (autonomy/auto-chain) and -m (merge at the end + cleanup + CI watch) through every route; auto-fix of raised findings (-f) and issue-raising (-ri) are downstream defaults, with -nf/--no-fix and -nori/--no-raise-issues as the forwarded opt-outs. -a and -m are orthogonal — full hands-off end-to-end is -a -m.

x-wt-teams

6
from Takazudo/claude-resources

Parallel multi-topic development using git worktrees, base branches, and Claude Code agent teams. Use when: (1) User wants to work on multiple related features in parallel, (2) User mentions 'worktree', 'base branch', 'parallel development', 'split into topics', or 'multi-topic'. FULLY AUTONOMOUS — creates worktrees, spawns teams, coordinates everything. Also supports Super-Epic child mode for [Epic] issues from /big-plan with '**Super-epic:** #N' markers (targets the super-epic base branch instead of main).

x-as-pr

6
from Takazudo/claude-resources

Start a development workflow as a draft PR. Creates a NEW branch from the current branch, empty start commit, draft PR targeting the current branch, then implements. ALWAYS creates a new branch by default — produces a nested PR-on-PR when the current branch already has one. Use when: (1) User says 'dev as pr', (2) User wants a PR-first workflow before coding, (3) User passes -s/--stay to reuse the current branch instead of nesting, (4) User passes a GitHub issue URL to implement, (5) User passes --make-issue/--issue to create an issue first. Logs progress via issue comments when an issue is linked.

watch-ci

6
from Takazudo/claude-resources

Watch GitHub PR CI checks in the background and notify on completion. Use when: (1) User wants to monitor CI/CD status, (2) User says 'watch CI', 'check CI', 'monitor checks', or 'wait for CI', (3) User wants to know when checks pass or fail. Runs a background gh polling shell loop (NOT a subagent — near-zero token cost), sends macOS notification on completion. Also handles merged PRs by watching the target branch CI.