How do I install the Propose Pr skill?

Run npx skillmds@latest add tomevault-io/propose-pr in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Propose Pr safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Propose Pr?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Propose Pr free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Propose Pr?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Propose Pr by tomevault-io — Agent Skill

Name: Propose Pr
Author: tomevault-io

File contents

What I do

Detect the current git branch and repository
Analyze git commits and code changes compared to the base branch (defaults to main)
Read and follow the .github/PULL_REQUEST_TEMPLATE.md or .github/pull_request_template.md if it exists
Generate a suggested PR title based on the changes
Generate a PR description following the template structure (if available)
Construct and open the GitHub PR comparison URL with pre-filled title and description

When to use me

Use this skill when you're ready to propose a pull request but want AI assistance with:

Writing a comprehensive PR description
Following the repository's PR template
Generating an appropriate PR title

I will NOT actually create or submit the PR - I only open the GitHub page with suggestions so you can review and submit it yourself.

Instructions

Get repository information:
- Run git remote get-url origin to get the repository URL
- Parse owner and repo name from the URL
- Get current branch with git branch --show-current
Verify branch is pushed to origin:
- Run git fetch origin to ensure remote refs are up to date
- Run git rev-parse --verify origin/<branch> to check if the branch exists on the remote
- If the branch is not pushed, notify the user and ask if they want you to push it with git push -u origin <branch>
- Do NOT proceed to open the PR URL until the branch exists on origin
Check for PR template:
- Look for .github/PULL_REQUEST_TEMPLATE.md or .github/pull_request_template.md
- If found, read the template file carefully
Analyze changes:
- Run git log main..HEAD --oneline (or appropriate base branch) to see commits
- Run git diff main...HEAD to see the actual code changes
- Understand what the PR is accomplishing
Generate PR content:
- Create a concise, descriptive PR title (one line summary)
- Write a PR description:
  - If a PR template exists: You MUST follow the template exactly and fill in each section appropriately. If a section does not apply, feel free to omit it.
  - If no template exists: Write a description that summarizes what changed and why, includes relevant context from commits and diffs, and uses proper markdown formatting.
Build and open URL:
- Use the bundled script (relative to this skill's base directory) to construct the URL:
```
<skill-base>/scripts/build-url.sh <owner> <repo> <base> <head> "<title>" "<body>"
```
- The script handles URL-encoding and outputs the full GitHub compare URL
- Open with: open "$(<skill-base>/scripts/build-url.sh ...)"

Dependencies

Before generating PR content, load the writing-voice skill and follow its guidelines.

Notes

If the base branch is not main, ask the user or try to detect it with git symbolic-ref refs/remotes/origin/HEAD
Keep the PR title under 72 characters if possible
Ensure the description is well-formatted markdown
If there are no commits on the current branch vs base, notify the user

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: propose-prdescription: Generates a GitHub PR title and description, then opens and autofills the new PR page. Use when user asks you to propose a PR.---## What I do- Detect the current git branch and repository- Analyze git commits and code changes compared to the base branch (defaults to `main`)- Read and follow the `.github/PULL_REQUEST_TEMPLATE.md` or `.github/pull_request_template.md` if it exists- Generate a suggested PR title based on the changes- Generate a PR description following the template structure (if available)- Construct and open the GitHub PR comparison URL with pre-filled title and description## When to use meUse this skill when you're ready to propose a pull request but want AI assistance with:- Writing a comprehensive PR description- Following the repository's PR template- Generating an appropriate PR titleI will NOT actually create or submit the PR - I only open the GitHub page with suggestions so you can review and submit it yourself.## Instructions1. **Get repository information**: - Run `git remote get-url origin` to get the repository URL - Parse owner and repo name from the URL - Get current branch with `git branch --show-current`2. **Verify branch is pushed to origin**: - Run `git fetch origin` to ensure remote refs are up to date - Run `git rev-parse --verify origin/<branch>` to check if the branch exists on the remote - If the branch is not pushed, notify the user and ask if they want you to push it with `git push -u origin <branch>` - Do NOT proceed to open the PR URL until the branch exists on origin3. **Check for PR template**: - Look for `.github/PULL_REQUEST_TEMPLATE.md` or `.github/pull_request_template.md` - If found, read the template file carefully4. **Analyze changes**: - Run `git log main..HEAD --oneline` (or appropriate base branch) to see commits - Run `git diff main...HEAD` to see the actual code changes - Understand what the PR is accomplishing5. **Generate PR content**: - Create a concise, descriptive PR title (one line summary) - Write a PR description: - **If a PR template exists**: You MUST follow the template exactly and fill in each section appropriately. If a section does not apply, feel free to omit it. - **If no template exists**: Write a description that summarizes what changed and why, includes relevant context from commits and diffs, and uses proper markdown formatting.6. **Build and open URL**: - Use the bundled script (relative to this skill's base directory) to construct the URL: ```bash <skill-base>/scripts/build-url.sh <owner> <repo> <base> <head> "<title>" "<body>" ``` - The script handles URL-encoding and outputs the full GitHub compare URL - Open with: `open "$(<skill-base>/scripts/build-url.sh ...)"`## DependenciesBefore generating PR content, load the `writing-voice` skill and follow its guidelines.## Notes- If the base branch is not `main`, ask the user or try to detect it with `git symbolic-ref refs/remotes/origin/HEAD`- Keep the PR title under 72 characters if possible- Ensure the description is well-formatted markdown- If there are no commits on the current branch vs base, notify the user---> Converted and distributed by [TomeVault](https://tomevault.io/claim/tylerbodway) — claim your Tome and manage your conversions.

Frequently asked questions

Propose Pr