pr

Name: pr
Author: tomevault-io

Engineering Community

Repo stars 0
Author repo skills-registry

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Create a GitHub pull request — pushes the current branch and opens a PR with auto-generated title and description. Use for any P…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Quick Reference”, “Workflow”, “Step 1: Check branch”, “Step 2: Check working directory”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name pr directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Quick Reference / Workflow / Step 1: Check branch” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Quick Reference

/pr                 # Create GitHub PR from current branch

Workflow

Step 1: Check branch

Run git branch --show-current. If on main, tell the user they cannot create a PR from the main branch and stop.

Run git log main..HEAD --oneline to check for commits ahead of main. If there are no commits AND the working directory is clean, tell the user there is nothing to create a PR for and stop.

Step 2: Check working directory

Run git status to check if the working directory is clean.

Clean: Proceed to Step 3.
Dirty (any staged, unstaged, or untracked changes): Ask the user:
1. Commit changes first — suggest using /ci, then stop and let the user run it.
2. Ignore local changes and continue creating the PR based on existing commits only.

Step 3: Push and create PR

Run git push -u origin HEAD to push the branch.
Run git log main..HEAD to analyze all commits on this branch. Generate a succinct, self-explanatory PR description from them.
Run gh pr create with a title following Conventional Commits pattern. Base branch is main.

Step 4: Request review agents

After the PR is created, automatically request code review from available review agents:

Run gh pr edit --add-reviewer @copilot to request Copilot code review.
If the command succeeds, note that Copilot review has been requested.
If it fails (e.g., Copilot not available for the repo), skip silently and continue.

Step 5: Show result

Display the PR URL to the user, along with the review request status.

Rules

This skill only creates PRs. It does not format, stage, or commit code.
The PR title must follow Conventional Commits pattern (e.g., feat:, fix:, refactor:).
If a PR already exists for this branch, display the existing PR URL instead of creating a new one.

Source: darknight/cc-deck — distributed by TomeVault.

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: Engineering
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @tomevault-io · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Plug-and-play
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Write / modify
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview pr-tomevault-io.preview

# Step 5: Show result

Display the PR URL to the user, along with the review request status.

SKILL.md SKILL.md

## Quick Reference
```
/pr                 # Create GitHub PR from current branch
```

## Workflow

### Step 1: Check branch

Run `git branch --show-current`. If on `main`, tell the user they cannot create a PR from the main branch and stop.

Run `git log main..HEAD --oneline` to check for commits ahead of main. If there are no commits AND the working directory is clean, tell the user there is nothing to create a PR for and stop.

### Step 2: Check working directory

Run `git status` to check if the working directory is clean.

- **Clean**: Proceed to Step 3.
- **Dirty** (any staged, unstaged, or untracked changes): Ask the user:
  1. Commit changes first — suggest using `/ci`, then stop and let the user run it.
  2. Ignore local changes and continue creating the PR based on existing commits only.

### Step 3: Push and create PR

1. Run `git push -u origin HEAD` to push the branch.
2. Run `git log main..HEAD` to analyze all commits on this branch. Generate a succinct, self-explanatory PR description from them.
3. Run `gh pr create` with a title following `Conventional Commits` pattern. Base branch is `main`.

### Step 4: Request review agents

After the PR is created, automatically request code review from available review agents:

1. Run `gh pr edit --add-reviewer @copilot` to request Copilot code review.
2. If the command succeeds, note that Copilot review has been requested.
3. If it fails (e.g., Copilot not available for the repo), skip silently and continue.

### Step 5: Show result

Display the PR URL to the user, along with the review request status.

## Rules

- This skill only creates PRs. It does not format, stage, or commit code.
- The PR title must follow Conventional Commits pattern (e.g., `feat:`, `fix:`, `refactor:`).

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Quick Reference → Workflow → Step 1: Check branch → Step 2: Check working directory → Step 3: Push and create PR → Step 4: Request review agents
terms    -> Clean · Dirty · Run git branch --show-current. · Run git log main..HEAD --oneline to check for commits ahead of main. · Run git status to check if the working directory is clean. · - Clean: Proceed to Step 3. · 1. Run git push -u origin HEAD to push the branch. · 1. Run gh pr edit --add-reviewer @copilot to request Copilot code review.
files/cmd -> git branch --show-current · main · git log main..HEAD --oneline · git status · /ci · git push -u origin HEAD · git log main..HEAD · gh pr create
body sha256 -> bad1917f37bf