ワンクリックでManusで任意のスキルを実行

gh-pr-list

スター2

フォーク0

更新日2026年6月5日 02:05

Generate a short, copy-paste friendly Slack message listing the user's open PRs in the current repo, split into "Ready for review" (non-draft) and "Drafts" sections, each as bullets with custom emoji and markdown-style links. Use when the user mentions PRs ready to review, Slack PR list, share my PRs on Slack, or wants a short message to ping reviewers.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

tomimor

tomimor/skills

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

GH PR List

Generate a Slack-ready message with the user's open PRs in the current repo, split into two sections: ready-for-review (non-draft) and drafts.

Resolve the current repo

Run from the user's cwd:

gh repo view --json nameWithOwner -q .nameWithOwner

If that fails, tell the user the cwd is not a GitHub repo (or gh is not authenticated) and stop.

Fetch PRs

gh pr list --repo OWNER/REPO --author @me --state open \
  --json number,title,url,isDraft,updatedAt

Split the result into two groups:

Ready: isDraft == false
Drafts: isDraft == true

If both groups are empty, report "No tienes PRs abiertos" and stop.

Output

Render the message directly in the chat using markdown (not inside a fenced code block — the user wants to see the rendered links and copy them to Slack, which accepts markdown-style links [title](url)).

Exact format:

Header Ready for review: + blank line + one bullet per ready PR: - :greenpr: [PR title](PR url)
Blank line.
Header Drafts: + blank line + one bullet per draft PR: - :draftpr: [PR title](PR url)

The leading - is required so the chat renders it as a proper bulleted list (without it, lines collapse into a single paragraph). Slack also accepts the - prefix as a bullet on paste.

Omit an entire section if its group is empty (do not print the header with no bullets under it).

Example (both sections):

Ready for review:

- :greenpr: [fix: limit long name fields and truncate in admin panel tables](https://github.com/owner/repo/pull/123)
- :greenpr: [fix: enforce HTTPS-only validation on webhook destination URL](https://github.com/owner/repo/pull/124)
- :greenpr: [feat: group system permissions and cap badge cells](https://github.com/owner/repo/pull/125)

Drafts:

- :draftpr: [wip: experimental rate limiter](https://github.com/owner/repo/pull/126)
- :draftpr: [chore: bump deps](https://github.com/owner/repo/pull/127)

Sort each section by updatedAt desc (most recent first).

Do not add a numbered list, intro paragraph, or commentary. The message is just the section headers, blank lines, and bullets.

このリポジトリの他の Skills

同じリポジトリ

share-ready

tomimor/skills

Audits and fully configures how a website looks when shared (Open Graph, Twitter/X cards, WhatsApp/Discord/Slack previews) and in the browser (title, favicons, theme-color, web manifest), generating missing assets and verifying the result locally. Use when setting up link previews, og:image, favicons, social sharing metadata, or when a shared link "looks wrong" on a platform.

2026-07-062

loop-react-doctor

tomimor/skills

Iterative React-health loop: inventory every React app in the repo, baseline with the latest react-doctor (pinned for the rest of the run), fix one root cause per iteration, and re-verify until every app scores 100/100 or every remaining finding has a user-approved written justification. Never silences findings with ignores, exclusions, or deleted behavior, and stops itself after two iterations without measurable progress. Use when the user mentions react-doctor, React health score, React anti-patterns cleanup, or driving a React codebase to a clean scan.

2026-07-042

loop-cve-audit

tomimor/skills

Iterative dependency-CVE remediation loop: scan with ecosystem-native advisory tooling, assess whether each high/critical finding is actually reachable (with call-path evidence, not vibes), fix the highest-risk reachable one with the smallest credible change, re-verify, and repeat. Terminates when no exploitable high/critical CVE remains or every remaining finding has an evidence-backed reachability assessment and an approved risk decision. Use when the user mentions CVEs, vulnerability scanning, dependency security, npm/pip/cargo audit, security patching, or wants a recurring dependency-security loop.

2026-07-042

ui-review

tomimor/skills

Orchestrates a comprehensive frontend UI review by running parallel analysis across typography, layout, accessibility, responsiveness, copy, visual polish, and design critique. Uses browser inspection for visual context. Produces a prioritized plan of small, concrete fixes -- never rewrites. Use when the user mentions UI review, frontend review, page review, design review, visual review, audit my page, or review my UI.

2026-06-252

pr-dashboard

tomimor/skills

Review open PRs authored by the user for a given repo, showing title, status, review state, open comments, CI checks, and recommended next steps. Use when the user mentions PR review, my PRs, open PRs, PR status, PR dashboard, or wants an overview of their pull requests.

2026-06-252

whats-missing

tomimor/skills

Surfaces the single most important blindspot in a plan, decision, or situation by checking whether the frame is right, generating candidates across 8 lenses (hidden constraints, false assumptions, second-order effects, stakeholders, blast radius, base rates, time horizon, counter-positions), then either committing to one or returning a calibrated "no blindspot" when none is load-bearing -- never a list of risks. Use when the user asks "what am I missing", "what's the most important thing I'm missing about this situation or decision", "what's my blindspot", "what's the biggest risk I'm not seeing", or wants a single sharp second opinion before committing.

2026-06-172

name	gh-pr-list
description	Generate a short, copy-paste friendly Slack message listing the user's open PRs in the current repo, split into "Ready for review" (non-draft) and "Drafts" sections, each as bullets with custom emoji and markdown-style links. Use when the user mentions PRs ready to review, Slack PR list, share my PRs on Slack, or wants a short message to ping reviewers.

GH PR List

Generate a Slack-ready message with the user's open PRs in the current repo, split into two sections: ready-for-review (non-draft) and drafts.

Resolve the current repo

Run from the user's cwd:

gh repo view --json nameWithOwner -q .nameWithOwner

If that fails, tell the user the cwd is not a GitHub repo (or gh is not authenticated) and stop.

Fetch PRs

gh pr list --repo OWNER/REPO --author @me --state open \
  --json number,title,url,isDraft,updatedAt

Split the result into two groups:

Ready: isDraft == false
Drafts: isDraft == true

If both groups are empty, report "No tienes PRs abiertos" and stop.

Output

Exact format:

Header Ready for review: + blank line + one bullet per ready PR: - :greenpr: [PR title](PR url)
Blank line.
Header Drafts: + blank line + one bullet per draft PR: - :draftpr: [PR title](PR url)

The leading - is required so the chat renders it as a proper bulleted list (without it, lines collapse into a single paragraph). Slack also accepts the - prefix as a bullet on paste.

Omit an entire section if its group is empty (do not print the header with no bullets under it).

Example (both sections):

Ready for review:

- :greenpr: [fix: limit long name fields and truncate in admin panel tables](https://github.com/owner/repo/pull/123)
- :greenpr: [fix: enforce HTTPS-only validation on webhook destination URL](https://github.com/owner/repo/pull/124)
- :greenpr: [feat: group system permissions and cap badge cells](https://github.com/owner/repo/pull/125)

Drafts:

- :draftpr: [wip: experimental rate limiter](https://github.com/owner/repo/pull/126)
- :draftpr: [chore: bump deps](https://github.com/owner/repo/pull/127)

Sort each section by updatedAt desc (most recent first).

Do not add a numbered list, intro paragraph, or commentary. The message is just the section headers, blank lines, and bullets.