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

始める

open-pr

スター4

フォーク0

更新日2026年7月15日 16:40

Commit, push, and open PR creation in the browser with an empty body for the human to fill in.

インストール

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

Manusで実行

ソース

collindutter

collindutter/dotfiles

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

ダウンロード

Manusで実行

Gather context

Get the base branch (usually main or master).
Get the commit messages: git log <base>...HEAD --format="%s" (used only to craft a concise title).

Commit and push

Run git status. If there are uncommitted changes you made in this session, commit them. Only commit files you changed; do not sweep in unrelated edits.
Use a conventional-commit message (e.g. feat:, fix:, refactor:), lowercase, imperative mood.
Push the branch: git push -u origin HEAD.

Create the PR

Write a short PR title in conventional-commit format (e.g. fix: handle missing library metadata on proxy nodes), max 72 characters.
Open PR creation in the browser with the title set and the body left empty. Do NOT create it directly and do NOT write a description; let the browser form (and any repo PR template) show for the human to fill in:
```
gh pr create --web --title "<title>"
```

このリポジトリの他の Skills

同じリポジトリ

review

collindutter/dotfiles

Run a code review sub-agent

2026-07-154

draft-review-comments

collindutter/dotfiles

Post a DRAFT (pending) GitHub PR review made of separate inline review comments anchored to the diff, each with an AI-assisted disclosure and GitHub deep-link permalinks that render as code snippets. Use when the user asks to "add a draft review comment", "post review findings as separate comments", "leave inline review comments", or wants reviewer findings turned into a pending PR review with deep links to the code.

2026-07-154

issue-pr

collindutter/dotfiles

Create a GitHub issue describing the root problem behind current changes, then open a PR that references it

2026-07-154

marp-to-branded-pptx

collindutter/dotfiles

Convert a Marp markdown deck into a fully editable, on-brand PowerPoint (.pptx) built on a Google Slides template's native layouts, carrying speaker notes across, ready to upload to Google Slides. Use when someone wants a Marp deck "in Google Slides", "in the company template", or "as an editable branded deck" rather than rasterized slide images.

2026-07-154

workmux

collindutter/dotfiles

Reference for the workmux CLI that manages git worktrees and tmux windows as isolated development environments. Use when the user mentions workmux, worktrees, or parallel agent workflows.

2026-07-154

coordinator

collindutter/dotfiles

Orchestrate multiple worktree agents. Spawn, monitor, communicate, and merge.

2026-07-084

name	open-pr
description	Commit, push, and open PR creation in the browser with an empty body for the human to fill in.
disable-model-invocation	true
allowed-tools	read bash

Commit any work, push the branch, and open PR creation in the browser. Do NOT write the PR body; leave it empty for the human to fill in.

Gather context

Get the base branch (usually main or master).
Get the commit messages: git log <base>...HEAD --format="%s" (used only to craft a concise title).

Commit and push

Run git status. If there are uncommitted changes you made in this session, commit them. Only commit files you changed; do not sweep in unrelated edits.
Use a conventional-commit message (e.g. feat:, fix:, refactor:), lowercase, imperative mood.
Push the branch: git push -u origin HEAD.

Create the PR

Write a short PR title in conventional-commit format (e.g. fix: handle missing library metadata on proxy nodes), max 72 characters.
Open PR creation in the browser with the title set and the body left empty. Do NOT create it directly and do NOT write a description; let the browser form (and any repo PR template) show for the human to fill in:
```
gh pr create --web --title "<title>"
```