Skill
coordinator
Orchestrate multiple worktree agents. Spawn, monitor, communicate, and merge.
@raineView SkillAgent Orchestration
Skill
/open-pr
Write a PR description using conversation context and open PR creation in browser.
Install
$ npx -y skills add raine/workmux --skill open-pr --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/open-pr
Context preview
The summary Claude sees to decide when to auto-load this skill.
Write a PR description using conversation context and open PR creation in browser.
SKILL.md
open-pr.SKILL.mdname: open-pr
description: Write a PR description using conversation context and open PR creation in browser.
disable-model-invocation: true
allowed-tools: Read, Bash, Glob, Grep
<!-- This is a starting point. Customize the template and guidelines to match your team's PR conventions. -->
Gather context
1. Get the base branch (usually `main` or `master`) 2. Get the diff: `git diff <base>...HEAD` 3. Get commit messages: `git log <base>...HEAD --format="%s"` 4. Read changed files to understand the broader context
Commit uncommitted changes
1. Run `git status` to check for uncommitted changes 2. If changes exist, commit them before proceeding
Write PR description
Use this template:
## Summary
[1-2 sentences: what this PR does and why]
## Changes
- [Key change 1]
- [Key change 2]
- [Key change 3]
## Testing
[How you verified it works]
Guidelines:
- Lead with a concise summary of what the PR does
- Explain the "why" before the "how"
- Use the conversation context to inform the description
- Include before/after comparisons for UI or performance changes
- Be direct and to the point
Create the PR
1. Write a short PR title (max 72 characters)
2. Ensure the branch is pushed:
git push -u origin HEAD
3. Open PR creation in browser (do NOT create directly):
gh pr create --web --title "<title>" --body "<body>"
Read more
name: open-pr description: Write a PR description using conversation context and open PR creation in browser. disable-model-invocation: true allowed-tools: Read, Bash, Glob, Grep
<!-- This is a starting point. Customize the template and guidelines to match your team's PR conventions. -->
Gather context
1. Get the base branch (usually `main` or `master`) 2. Get the diff: `git diff <base>...HEAD` 3. Get commit messages: `git log <base>...HEAD --format="%s"` 4. Read changed files to understand the broader context
Commit uncommitted changes
1. Run `git status` to check for uncommitted changes 2. If changes exist, commit them before proceeding
Write PR description
Use this template:
## Summary [1-2 sentences: what this PR does and why] ## Changes - [Key change 1] - [Key change 2] - [Key change 3] ## Testing [How you verified it works]
Guidelines:
- Lead with a concise summary of what the PR does
- Explain the "why" before the "how"
- Use the conversation context to inform the description
- Include before/after comparisons for UI or performance changes
- Be direct and to the point
Create the PR
1. Write a short PR title (max 72 characters)
2. Ensure the branch is pushed:
git push -u origin HEAD
3. Open PR creation in browser (do NOT create directly):
gh pr create --web --title "<title>" --body "<body>"
Ships withworkmux-status
git worktrees + tmux windows for zero-friction parallel dev
Get the whole plugin
Stats
2,794
Stars
332
Forks
Active
Maintenance
Rust
Language
MIT
License
3d ago
Last commit
11mo ago
Created
11h ago
Added
Repo: raine/workmux
Other skills on workmux-status.
@raineView Skill