open-pr
Skill0 starsChanged 6 months agoMITView on GitHub
Open the pull request for the branch you are working on in the browser via `gh pr view --web`. Trigger when the user says: "PRを開いて", "PRをブラウザで", "PRを見せて", "open pr", "open the PR", "show me the PR", or similar phrases requesting to open the working pull request in the browser.
62 other projects use a version of this.
Adopted by
Most recently taken up by
- 0xdeafcafe/skillstheir own version, first seen Nov 6, 2026
- pascalorg/editortheir own version, first seen Nov 6, 2026
- Significant-Gravitas/AutoGPTtheir own version, first seen Nov 4, 2026
- angusfretwell/skillstheir own version, first seen Nov 4, 2026
- mongodb/docstheir own version, first seen Nov 2, 2026
- elpiarthera/vantage-startertheir own version, first seen Nov 1, 2026
Used with
Projects with it also use review-change, commit-push and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
thlaureSkillreview-change
Use this skill when the user asks for a code review, a correctness pass, a check before PR, or asks whether a Signalist change follows project conventions.
Also in 4 projects that use this
DataCoveySkillcommit-push
Commit and push the changes made on this chat session to the current branch. Use best practices from Conventional Commits.
Also in 3 projects that use this
Codagent-AISkillimplement-change
Implements an approved change in one continuous session, with tiered test runs. Use when asked to implement a change from its approved definition, or to invoke codagent:implement-change.
Also in 3 projects that use this
saffron-healthSkilladdress-review
Address PR review comments systematically. Use when responding to code review feedback on a pull request.
Also in 3 projects that use this
DockerSkillreview-pr
Review one or more incoming Docker documentation pull requests as a maintainer. Independently validate technical claims, assess editorial fit and information architecture, choose a verdict, and draft exact inline or PR-wide feedback behind a confirmation gate. Use for requests such as "review PR 123", "is this PR correct?", "does this information belong here?", "validate this PR", or "help review backlog PRs". Do not use to maintain or fix a PR you own; use maintain-pr for that.
Also in 10 projects that use this
SentrySkillwrite-tests
Write tests following project conventions. Use when adding new tests or modifying existing ones.
Also in 4 projects that use this
Other versions62 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 62
- Significant-Gravitas/AutoGPT★ 188ksame name
- storybookjs/storybook★ 91ksame name
- pascalorg/editor★ 25ksame name
- dask/dask★ 14ksame name
- polarsource/polar★ 10ksame name
- cloudflare/agents★ 6ksame name
- Kiln-AI/Kiln★ 5.3ksame name
- analogjs/analog★ 3.2ksame name
- raine/workmux★ 3ksame name
- Akylas/OSS-DocumentScanner★ 2.6ksame name
52 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- acceptance-testSkill
- commitSkill
- dependabotSkill
- design-docSkill
- initSkill
- pick-issueSkill
- qaSkill
- review-docsSkill
- security-alertSkill
- shipSkill
- start-devSkill
- sync-docsSkill
- sync-worktreesSkill
- test-perspectiveSkill
- triage-statusSkill
The file
Files
Open PR Skill
作業中のブランチに対応する PR を gh pr view --web でブラウザに開く。
毎回コマンドを手で打つ手間をなくすためのショートカット。
手順
- 引数が渡されていればそれを優先する。PR 番号またはブランチ名とみなして
gh pr view <引数> --webを実行し、終了する(例:/open-pr 42) - 引数がなければ対象ブランチを決める:
- カレントディレクトリ(またはこのセッションで作業中の worktree)の
ブランチが
main/master以外なら、それを対象にする - main 上にいる場合は
git worktree listで.claude/worktrees/配下の worktree を列挙し、各ブランチの PR をgh pr view <branch> --json url,state,titleで確認する- open な PR が 1 件だけならそれを対象にする
- 複数あれば AskUserQuestion でどれを開くか選んでもらう
- 0 件なら
gh pr list --author @meの結果を見せて、開ける PR が ないことを伝えて終了する
- カレントディレクトリ(またはこのセッションで作業中の worktree)の
ブランチが
gh pr view <branch> --webを実行し、開いた PR のタイトルと URL を ユーザーに伝える
注意
- ブラウザを起動できない環境(ヘッドレス等)で
--webが失敗したら、gh pr view <branch> --json url -q .urlで URL だけ表示する
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

