// Assemble a pull request that follows this repo's PR template, then open it as a draft. Use when the user wants to open, create, submit, or raise a PR for the current branch.
Wire yet-another-statusline into Claude Code — writes statusLine.command to ~/.claude/settings.json. Run once after plugin install, and again after every upgrade to update the versioned path.
Unwire yet-another-statusline from Claude Code — removes statusLine.command from ~/.claude/settings.json and deletes the renderer's runtime state. Run before (or after) `claude plugin uninstall yas`, which only deletes the plugin cache and leaves the statusLine config behind.
Edit the Claude Code statusline renderer safely. Use when touching claude/statusline_command.py, claude/statusline/*.py, claude/statusline-command.sh, or related tests. Covers the layered renderer (GradientEngine / BorderRenderer / Renderer), the LayoutSpec/RowSpec layout pipeline, Nerd Font PUA glyph hazards, border/elbow column math, and the demo-based visual check.
| name | yas-pr |
| description | Assemble a pull request that follows this repo's PR template, then open it as a draft. Use when the user wants to open, create, submit, or raise a PR for the current branch. |
Fill in this repo's PR template from the current branch, then open a draft PR. Do not invent the template structure — read it from the repo so the two never drift.
Sanity-check the branch and hooks. Confirm the current branch is not main and has
commits ahead of origin/main. If it's main or has no diff, stop and tell the user. Also
check git config --local --get core.hooksPath; if it isn't .github/hooks, offer to run
make hooks so the contributor gets pre-commit checks (don't enable it without their yes).
Read the template. Load .github/pull_request_template.md. This is the single source of
truth for the section structure — mirror its headings exactly.
Draft Context and Changes. From git diff main...HEAD plus the conversation:
.scratch/<feature>/...) if one exists.Embed system info. Run make pr-info and paste its output into the System info fenced
block verbatim.
Run tests. Run uv run pytest. If green, tick the tests checkbox. If red, show the
failures and ask the user whether to fix first or proceed. Optionally also run uv run ruff check and uv run mypy . and note results.
Benchmark. Run make bench (times this branch vs main via a throwaway git worktree).
If hyperfine is not on PATH, bench.py prints an install hint and falls back to a Python
timer — before letting it fall back, offer to install hyperfine (apt/brew/cargo) and ask
the user; only fall back if they decline. Paste the paste-ready table into the Benchmark
block. Tick "N/A — no performance-relevant change" instead only for docs/config-only PRs.
Screenshots. You cannot attach images via gh. Remind the user that for any rendering
change they should drag before/after images into the draft's web UI before marking it ready.
For rendering changes, make demo/img can produce snapshots to use.
Confirm, then create the draft. Show the fully assembled body. After the user confirms,
run gh pr create --draft with that body. Print the PR URL and tell the user to add
screenshots and click "Ready for review" when done.
gh pr create --draft is an outward-facing action: never run it before the user confirms the
body.