pr
- Repo stars 534
- Author updated Live
- Author repo couchers
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @Couchers-org · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Env read
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: pr
description: Commit all changes, push to a new branch, and create a pull request using the repo's PR template…
category: engineering
runtime: no special runtime
---
# pr output preview
## PART A: Task fit
- Use case: Commit all changes, push to a new branch, and create a pull request using the repo's PR template. Use when the user says to make a PR or submit changes. Create a branch, commit, push, and open a PR for the current changes. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Steps / 1. Assess the current state / 2. Determine the branch name” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Commit all changes, push to a new branch, and create a pull request using the repo's PR template. Use when the user says to make a PR or submit changes. Create a branch, commit, push, and open a PR for the current changes. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Steps / 1. Assess the current state / 2. Determine the branch name” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, read environment variables; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, read environment variables; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source mentions slash commands such as `/app`; use them first when your agent supports command triggers.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, read environment variables.
Start with a small task and check whether the result follows “Steps / 1. Assess the current state / 2. Determine the branch name”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: pr
description: Commit all changes, push to a new branch, and create a pull request using the repo's PR template…
category: engineering
source: Couchers-org/couchers
---
# pr
## When to use
- Commit all changes, push to a new branch, and create a pull request using the repo's PR template. Use when the user sa…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Steps / 1. Assess the current state / 2. Determine the branch name” and keep inference separate from source facts.
- read files, write/modify files, read environment variables; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "pr" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Steps / 1. Assess the current state / 2. Determine the branch name
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, read environment variables | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Create a Pull Request
Create a branch, commit, push, and open a PR for the current changes.
Steps
1. Assess the current state
Run in parallel:
git status(never use-uall)git diffandgit diff --stagedto understand all changesgit log --oneline -5to see recent commit message style
Identify which files should be committed. Do NOT commit files that are:
- Scratch/debug/temporary files
- Files containing secrets (
.env, credentials, etc.)
If there are no meaningful changes to commit, tell the user and stop.
2. Determine the branch name
Branch names in this repo follow the pattern: <area>/<type>/<short-description>
Where:
<area>is one of:backend,web,frontend,mobile,devops,docs, or another area that matches the changed files. For cross-cutting changes spanning multiple areas, pick the one that best describes the change.<type>is one of:feature,bugfix,fix,refactor, or similar<short-description>is a short kebab-case description
Infer area and type from the changed files and the nature of the changes. Never use a username as the area.
3. Run linters and formatters
Before committing, run the appropriate linters and formatters for the changed areas:
- Backend:
make formatandmake mypyfrom/app/backend - Web/Frontend: lint/format as appropriate
Fix any issues before proceeding. If linters produce changes, include those in the commit.
4. Create the branch and commit
If there are already commits on the current branch and no uncommitted changes remain (e.g. changes were already committed earlier), skip the commit and proceed to pushing.
Otherwise:
git checkout -b <branch-name>
git add <specific files> # add only the relevant files by name
git commit -m "<message>"Write a concise commit message (1-2 sentences) that describes what changed and why.
5. Push the branch
git push -u origin <branch-name>6. Create the PR
Read the PR template from .github/pull_request_template.md in this repo. Fill it in based on the actual changes:
Fill in the description at the top (what and why)
Fill in the Testing section with what was done or what should be done
Include the appropriate checklist(s) — backend, web, or both — based on which areas were changed. Remove checklists that don't apply.
Keep the "For maintainers" section as-is
Append the following note as the very last line of the PR body, after the "For maintainers" section (separated by a blank line):
_This PR was created with the Couchers PR skill._
gh pr create --base develop --title "<short title>" --body "$(cat <<'EOF'
<filled-in PR template>
_This PR was created with the Couchers PR skill._
EOF
)"7. Report back
Tell the user the PR URL when done.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review