Skills Guide

Create a Pull Request with workon

VerifiedSafe

Creates a pull request using the workon CLI. It gathers context, offers code review, and generates content for the PR before requiring explicit user approval. Helps when code is ready for review or the user says 'create a PR'.

Download and use
Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude Code
#pull-request#code-review#git#github#workon

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerRefactoring

Automated summary

Automatically creates a pull request on GitHub using the workon CLI, after generating content and obtaining user approval.

Strengths

  • Automates PR creation with title, summary, description, and testing instructions.
  • Includes a code review step before submission.
  • Automatically extracts ticket ID from branch name.
  • Leverages existing PR templates to follow project conventions.

Limitations

  • Requires the workon CLI to be installed and configured.
  • Depends on a specific branch naming convention (username/{ticketid}/...).
  • Does not handle complex cases like multi-step PRs or reviewer interactions.
When to use it

When you are ready to submit code for review and want a structured PR with a preliminary code review.

When not to use it

If the workon CLI is not available or if the PR requires custom manual formatting not supported.

Security analysis

Safe
Quality score85/100

The skill uses safe commands (git diff, git log, cat, workon) to create a pull request. There are no destructive or exfiltrating actions, and it requires explicit user approval before pushing.

No concerns found

How this analysis is made

Examples

Create PR from current branch
Create a pull request from this branch
Open a draft PR
Open a draft pull request for these changes

name: workon-pr description: Create a pull request using the workon CLI. Use when the user says "workon pr", "create a PR", "open a PR", or indicates code is ready for review. disable-model-invocation: true allowed-tools: Bash(workon:), Bash(gh:), Bash(git:), Bash(cat:), Read

Create a Pull Request

Steps

  1. Gather context by running these commands:

    • Read the PR template: cat .github/PULL_REQUEST_TEMPLATE.md
    • Get the diff: git diff origin/HEAD...HEAD or git diff main...HEAD
    • Get commit history: git log --oneline origin/HEAD...HEAD or git log --oneline main...HEAD
    • Extract ticket ID from branch name (format: username/{ticketid}/...)

  2. Offer code review (ask the user):

    • Before creating the PR, ask if they'd like you to run a code review first
    • If yes, review the changes for issues, improvements, and potential bugs
    • Address any findings before proceeding

  3. Generate content for each section (you are responsible for generating this):

    • Title: Concise description of the change (often matches ticket name)
    • Summary: 1-2 sentences describing what changed and why
    • Description: Detailed explanation referencing specific files/functions changed
    • How to Test: Step-by-step verification instructions with expected outcomes

  4. Get explicit user approval:

    • Show the user the PR details (title, summary, description, testing instructions)
    • Ask: "Ready to create this PR and push to GitHub?"
    • WAIT for explicit confirmation (e.g., "yes", "go ahead", "create it")
    • Do NOT proceed until you receive explicit approval

  5. Create the PR after receiving approval:

    workon pr -y --title "..." --summary "..." --ticket "..." --description "..." --testing "..."
    • Always use -y flag to skip confirmation (user already approved)
    • Add --draft if user asks for draft PR or mentions "draft", "WIP", "work in progress"
    • Ticket ID is auto-extracted from branch if not provided
    • Base branch is auto-detected (main or master)
    • Use --base <branch> to override if needed

Important Notes

  • Do NOT modify the "Best Practices" checklist section in the PR template
  • The workon CLI fills in the PR template sections automatically

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/create-a-pull-request-with-workon-mmh8qqca/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/create-a-pull-request-with-workon-mmh8qqca' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/create-a-pull-request-with-workon-mmh8qqca/download' --output '.skill-downloads/create-a-pull-request-with-workon-mmh8qqca/SKILL.md.part' && mv '.skill-downloads/create-a-pull-request-with-workon-mmh8qqca/SKILL.md.part' '.skill-downloads/create-a-pull-request-with-workon-mmh8qqca/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Bash(workon:*), Bash(gh:*), Bash(git:*), Bash(cat:*), Read

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/create-a-pull-request-with-workon-mmh8qqca/SKILL.md' && test -s '.skill-downloads/create-a-pull-request-with-workon-mmh8qqca/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/workon-pr' && cp -R '.skill-downloads/create-a-pull-request-with-workon-mmh8qqca' '.claude/skills/workon-pr'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/create-a-pull-request-with-workon-mmh8qqca'

openskills read 'create-a-pull-request-with-workon-mmh8qqca'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/create-a-pull-request-with-workon-mmh8qqca/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

React Hook Form Best Practices

Development

Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.

Claude CodeCursorWindsurf+2intermediateSafe 108,623
Skills Guide Bot

Emotion to Mantine Migration

Development

Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.

Claude CodeCursorWindsurf+1intermediateSafe 48,981
Skills Guide Bot

Scope Creep Detector

Development

Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.

Claude CodeCursorCodexintermediateSafe 135,015
Skills Guide Bot