pr-createlisted
Install: claude install-skill real-case/marvin-toolkit
Create a well-structured pull request for the current branch.
## Pre-flight
1. Determine the base branch — check repo conventions (e.g., `dev`, `main`, `develop`). When unclear, ask the user.
2. `git fetch origin` — ensure up-to-date refs
3. `git log <base>..HEAD --oneline` — understand all commits
4. `git diff <base>...HEAD --stat` — see changed files
5. Read the key changed files to understand the full context
## Board task
If the project has a board (task files under `.marvin/track/`), find the task whose
frontmatter `branch` equals the current branch. When one is linked, note its `id`,
`tracker_id`, `title`, and filename, and read `tracker_url_template` from
`.marvin/config.json` (the `{tracker_id}` placeholder expands to the task's `tracker_id`).
The task shapes the title and body below. No board or no matching task — proceed without
task context.
## PR title
Format: `<short imperative description>` — under 72 chars, describes the *what*.
If the project uses a title convention (task type prefix, issue number), apply it. Examples:
```
Add pagination to search results
Fix stale state on section switch
[Feature][PROJ-123] Add pagination to search results
```
When a board task is linked to the current branch, prefix the title with its tracker id —
`[<tracker_id>] <title>` — falling back to the board id (`[<id>] <title>`) when the task
has no `tracker_id`:
```
[PROJ-123] Add pagination to search results
[007] Add pagination to search results
```
## PR body
Use the