Prepare and Submit Changes

VerifiedCaution

Commit changes, bump version, update changelog, and open a pull request.

Sby Skills Guide Bot
DevOpsIntermediate
7/22/2026
Claude Code
#git#pull-request#changelog#versioning#commit

Recommended for

Automated summary

This skill walks through preparing a contribution: creating a branch, committing with conventional messages, bumping the version, updating the CHANGELOG, and opening a pull request via gh.

Strengths

  • Chains the full contribution flow end to end, from branch creation to PR
  • Enforces conventional commit messages and a consistent version bump (patch, minor, major)
  • Reuses the /changelog skill for user-facing changes
  • States clear guardrails: the user's git identity, no Claude trailers, and stopping when tests fail

Limitations

  • Assumes a GitHub repository with the gh CLI configured and a version file such as pyproject.toml
  • Delegates changelog generation to another skill whose availability isn't guaranteed
  • Test verification depends on a make test target or equivalent you must provide
When to use it

Use it when a batch of changes is ready to be shipped as a committed branch with version bump, changelog, and pull request.

When not to use it

Avoid it on repositories not hosted on GitHub, without gh installed, or when tests can't be run to validate state before committing.

Security analysis

Caution
Quality score82/100

The skill is a straightforward Git/PR workflow with no obfuscation, secret exfiltration, destructive filesystem commands, or safety-disabling instructions. It does use powerful, remotely mutating commands such as `git push` and `gh pr create`, so it warrants caution rather than being rated fully safe.

Findings
  • •Instructs committing, pushing to a remote, and opening a PR, which can mutate shared repository state without an explicit confirmation step beyond force-push.
  • •Uses `gh pr create --fill`, which may derive PR content from local commit data and branch state; legitimate but network/repo-affecting.
  • •No declared allowed-tools, yet the workflow assumes git, gh, make, and file-edit capabilities.
How this analysis is made

Examples

Ship a finished feature
The remote file sync is done and tests pass — commit it on a feature branch, bump the minor version, update the changelog, and open a PR.
Prepare a bug fix PR
I fixed the timeout on large files. Run /pr: branch, commit with a fix: message, patch bump, changelog entry, and create the pull request.
Review state before submitting
Check git status and run the tests first, then if everything is green commit my changes and open a PR for me.

name: pr description: Commit changes, bump version, update changelog, and open a PR

/pr - Prepare and Submit Changes

Purpose

Commit changes to a feature branch, bump version if needed, update changelog, and open a PR.

Before Starting

  • Check for uncommitted changes: git status --porcelain
  • Ensure tests pass: make test or equivalent
  • Confirm current branch (create one if on main)

Process

  1. Create or verify feature branch

    If on main, create a branch from the work context:

    git checkout -b <descriptive-branch-name>
    
  2. Stage and commit changes

    Use the user's git identity (never sign as Claude, no Co-authored-by). Write conventional commit messages:

    • feat: add remote file sync
    • fix: resolve timeout on large files
  3. Bump version if warranted

    • Bug fixes → patch
    • New features → minor
    • Breaking changes → major

    Update version in pyproject.toml (or equivalent).

  4. Update CHANGELOG.md

    Use /changelog skill to generate entry if changes are user-facing.

  5. Push and create PR

    git push -u origin <branch>
    gh pr create --fill
    

    PR description should summarize changes. Link issues if referenced in commits.

Notes

  • Don't add "Signed-off-by" or "Co-authored-by: Claude" trailers
  • Ask before force-pushing
  • If tests fail, stop and report

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/prepare-and-submit-changes-mrwak8wc/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/prepare-and-submit-changes-mrwak8wc' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/prepare-and-submit-changes-mrwak8wc/download' --output '.skill-downloads/prepare-and-submit-changes-mrwak8wc/SKILL.md.part' && mv '.skill-downloads/prepare-and-submit-changes-mrwak8wc/SKILL.md.part' '.skill-downloads/prepare-and-submit-changes-mrwak8wc/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/prepare-and-submit-changes-mrwak8wc/SKILL.md' && test -s '.skill-downloads/prepare-and-submit-changes-mrwak8wc/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/pr' && cp -R '.skill-downloads/prepare-and-submit-changes-mrwak8wc' '.claude/skills/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/prepare-and-submit-changes-mrwak8wc'

openskills read 'prepare-and-submit-changes-mrwak8wc'

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/prepare-and-submit-changes-mrwak8wc/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