Automated summary
Creates a simple pull request from staged changes with an automatically generated commit message.
Strengths
- Checks preconditions before acting: everything staged, on main, and main up to date
- Drafts a commit message focused on the "why" and asks for confirmation before committing
- Deterministic branch naming derived from git user.name plus a descriptive slug
- Pushes the branch, opens the PR via gh, and reports the PR URL back to the user
Limitations
- Assumes main is always the base branch, so it breaks on repos defaulting to master or on feature-branch workflows
- Requires GitHub plus an authenticated gh CLI; no GitLab or Bitbucket support
- Aborts on unstaged changes and leaves the user to run git add manually
Use it when your changes are already staged on main and you want a branch, commit, and GitHub PR in one pass.
Avoid it for multi-commit PRs, non-GitHub remotes, or repos where main is not the base branch.
Security analysis
CautionThe skill performs legitimate Git and GitHub CLI operations, but it requires shell/network tools and can mutate the local repository and remote state by pulling, committing, pushing, and opening a PR. There is no evidence of destructive commands, secret exfiltration, obfuscation, or safety-disabling behavior, so it is caution rather than risky.
- •No allowed-tools declared even though the skill requires shell execution of git and gh commands.
- •Runs network-affecting commands: git pull origin main, git push, and gh pr create.
- •git pull and branch checkout can modify the user's working tree if preconditions are not perfectly enforced.
Examples
Create a simple PR from my staged changes.I've staged the retry-logic fix on main — commit it on a new branch and open a PR.Everything is staged for the README typo fix. Generate the commit message, branch, and open the PR.name: simple-pr description: Create a simple PR from staged changes with an auto-generated commit message disable-model-invocation: true
Simple PR
Follow these steps to create a simple PR from staged changes:
Step 1: Check workspace state
Run: git status
Verify that all changes have been staged (no unstaged changes). If there are unstaged changes, abort and ask the user to stage their changes first with git add.
Also verify that we are on the main branch. If not, abort and ask the user to switch to main first.
Step 2: Ensure main is up to date
Run: git pull origin main
This ensures we're working from the latest code.
Step 3: Review staged changes
Run: git diff --cached
Review the staged changes to understand what the PR will contain.
Step 4: Generate commit message
Based on the staged changes, generate a concise commit message (1-2 sentences) that describes the "why" rather than the "what".
Display the proposed commit message to the user and ask for confirmation before proceeding.
Step 5: Create a new branch
Get the git username: git config user.name | tr ' ' '-' | tr '[:upper:]' '[:lower:]'
Create a short, descriptive branch name based on the changes (e.g., fix-typo-in-readme, add-retry-logic, update-deps).
Create and checkout the branch: git checkout -b {username}/{short-descriptive-name}
Step 6: Commit changes
Commit with the message from step 3:
git commit -m "{commit-message}"
Step 7: Push and open a PR
Push the branch and open a PR:
git push -u origin {branch-name}
gh pr create --title "{commit-message-title}" --body "{longer-description-if-needed}"
Report the PR URL to the user when complete.
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 filesThis 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.mdFrom the root of a test project, save the file as .skill-downloads/simple-pr-creation-mm5t89nu/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/simple-pr-creation-mm5t89nu' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/simple-pr-creation-mm5t89nu/download' --output '.skill-downloads/simple-pr-creation-mm5t89nu/SKILL.md.part' && mv '.skill-downloads/simple-pr-creation-mm5t89nu/SKILL.md.part' '.skill-downloads/simple-pr-creation-mm5t89nu/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.
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/simple-pr-creation-mm5t89nu/SKILL.md' && test -s '.skill-downloads/simple-pr-creation-mm5t89nu/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/simple-pr' && cp -R '.skill-downloads/simple-pr-creation-mm5t89nu' '.claude/skills/simple-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 installationopenskills install './.skill-downloads/simple-pr-creation-mm5t89nu'openskills read 'simple-pr-creation-mm5t89nu'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 syncManual 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/simple-pr-creation-mm5t89nu/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.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.