Skill

pr-make-suggestion-to-pr

Creates separate suggestion PRs from unstaged changes, grouped by topics like formatting or refactoring, each based on the current PR branch. Use after /pr-make-suggestion-edit or on 'suggestion to pr' request.

Git

Github

git-workflow

npx claudepluginhub takazudo/claude-resources

Tool Access

This skill uses the workspace's default tool permissions.

Preview

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

SKILL.md

Similar Skills

cache-components

139.3k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

Stats

Stars7

Forks0

Last CommitMay 7, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

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

Check current branch and PR
View all unstaged changes: git status, git diff --stat, git diff
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:

Create a new branch based on CURRENT branch (not base branch)

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

Selectively stage only files for this topic

Create commit following project conventions

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

Push and create PR targeting the original PR branch

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

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