create-pr | claudefiles | ClaudePluginHub

Skill

Community

create-pr

From claudefiles

1

Description

Create PRs for code changes based on user preferences. Invoke when users requests to create a pull request.

AI Summary

Generates pull request descriptions in markdown based on code changes and user preferences.

Install

1

Add the repository(one-time)

$

/plugin marketplace add DieGopherLT/claude-kit

2

Install the plugin

$

/plugin install diegopherlt-claude-kit@DieGopherLT/claude-kit

Tool Access

This skill inherits all available tools. When active, it can use any tool Claude has access to.

Supporting Assets

View in Repository

formats/standard.md

Skill Content

Create a pull request text on a file named <current-branch>-PR.md on English language following one of the formats defined in formats

Create the file at the root of the CWD.

Posible formats

standard: When none of the other formats apply.

If in doubt between two or more formats and standard is not included, ask the user for clarification.

Temporal note: More formats will be added in the future, just use standard for now.

Guidelines

Be concise, fulfill the information on formats with the minimal required information.
- If the reader of it needs more context, let them ask for it, so do not bloat the file.
Use markdown syntax.
Be aware of the dimension of the changes done.
- A small fix or feature should not have a very big PR description.
- A big refactor or feature should have a more detailed PR description.

How to measure size the changes

Small: 1-4 files changed, up to 150 lines changed.
- PR sections will likely have one to two sentences.
Medium: 5-7 files changed, 150-700 lines changed.
- Try to explain the reasoning behind the changes.
- PR sections will likely have up to 3 paragraphs.
Large: 8+ files changed, 700+ lines changed.
- PR sections will likely have up to 5 paragraphs.
- There is a high chance that there are going to be multiple elements involved, explain how they interconnect.
- Focus on a explaining the high level details of the changes

The assistant have the proper criteria and judgment to determine the dimension of changes done outside of the quantitative metrics provided; appeal the quantitative metrics as a guideline, not a rule.

Links

GitHub Stats

0 forks

Updated 4 hours ago

Similar Skills

Command Development

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.

56.3k

Agent Development

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.

56.3k

Hook Development

This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.

56.3k