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

pr-draft-summary

スター2

フォーク0

更新日2026年4月7日 07:52

Generate a PR-ready summary block with branch suggestion, title, and description. Use in the final handoff after moderate-or-larger code changes; skip for trivial or conversation-only tasks.

インストール

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

Manusで実行

ソース

pproenca

pproenca/unifi-mcp

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

ダウンロード

Manusで実行

PR Draft Summary

Purpose

Produce the PR-ready summary after substantive code work: a concise summary plus a PR title and draft description. The block should be ready to paste into a PR.

When to Trigger

The task is finished and it touched runtime code (src/), tests, docs with behavior impact, or build configuration.
Default final handoff step for substantive code work.
Skip for trivial or conversation-only tasks, or when the user says not to.

Inputs to Collect Automatically

Current branch: git rev-parse --abbrev-ref HEAD
Working tree: git status -sb
Untracked files: git ls-files --others --exclude-standard
Changed files: git diff --name-only and git diff --name-only --cached
Latest release tag: git tag -l 'v*' --sort=-v:refname | head -n1
Base reference: git rev-parse --abbrev-ref --symbolic-full-name @{upstream} 2>/dev/null || echo origin/main
Commits ahead: git log --oneline --no-merges ${BASE_COMMIT}..HEAD

Workflow

Run the commands above without asking the user.
If no changes detected, say so and skip the block.
Classify as feature, fix, refactor, or docs and flag backward-compatibility risk against the latest release tag.
Summarize changes in 1-3 sentences using key paths and diff stats.
Choose the lead verb: feature → adds, fix → fixes, refactor → improves, docs → updates.
Suggest a branch name if on main: feat/<slug>, fix/<slug>, or docs/<slug>.
Draft using the template below.

Output Format

# Pull Request Draft

## Branch name suggestion

git checkout -b <kebab-case, e.g., feat/add-firewall-tools>

## Title

<single-line imperative title, e.g., "feat: add firewall management tools">

## Description

<Start with "This pull request adds/fixes/improves ...", explain the change, any behavior changes or considerations. No need to list tests.>

このリポジトリの他の Skills

同じリポジトリ

build-mcp-server

pproenca/unifi-mcp

This skill should be used when the user asks to "build an MCP server", "create an MCP", "make an MCP integration", "wrap an API for Claude", "expose tools to Claude", "make an MCP app", or discusses building something with the Model Context Protocol. It is the entry point for MCP server development — it interrogates the user about their use case, determines the right deployment model (remote HTTP, MCPB, local stdio), picks a tool-design pattern, and hands off to specialized skills.

2026-04-072

code-change-verification

pproenca/unifi-mcp

Run the verification stack (format, lint, typecheck, test) when changes affect runtime code, tests, or build config.

2026-04-072

docs-sync

pproenca/unifi-mcp

Audit documentation coverage by comparing implementation against docs/. Use when asked to check doc coverage, sync docs with code, or after significant API surface changes. Produce a report and ask for approval before editing.

2026-04-072

implementation-strategy

pproenca/unifi-mcp

Decide how to implement runtime and API changes before editing code. Use when a task changes exported APIs, MCP tool definitions, runtime behavior, or configuration, and you need to choose the compatibility boundary and implementation shape.

2026-04-072

typescript

pproenca/unifi-mcp

This skill should be used when the user asks to "optimize TypeScript performance", "speed up tsc compilation", "configure tsconfig.json", "fix type errors", "improve async patterns", or encounters TS errors (TS2322, TS2339, "is not assignable to"). Also triggers on .ts, .tsx, .d.ts file work involving type definitions, module organization, or memory management. Does NOT cover TypeScript basics, framework-specific patterns, or testing.

2026-04-072

PR Draft Summary

Purpose

Produce the PR-ready summary after substantive code work: a concise summary plus a PR title and draft description. The block should be ready to paste into a PR.

When to Trigger

The task is finished and it touched runtime code (src/), tests, docs with behavior impact, or build configuration.

Default final handoff step for substantive code work.

Skip for trivial or conversation-only tasks, or when the user says not to.

Inputs to Collect Automatically

Current branch: git rev-parse --abbrev-ref HEAD

Working tree: git status -sb

Untracked files: git ls-files --others --exclude-standard

Changed files: git diff --name-only and git diff --name-only --cached

Latest release tag: git tag -l 'v*' --sort=-v:refname | head -n1

Base reference: git rev-parse --abbrev-ref --symbolic-full-name @{upstream} 2>/dev/null || echo origin/main

Commits ahead: git log --oneline --no-merges ${BASE_COMMIT}..HEAD

Workflow

Run the commands above without asking the user.

If no changes detected, say so and skip the block.

Classify as feature, fix, refactor, or docs and flag backward-compatibility risk against the latest release tag.

Summarize changes in 1-3 sentences using key paths and diff stats.

Choose the lead verb: feature → adds, fix → fixes, refactor → improves, docs → updates.

Suggest a branch name if on main: feat/<slug>, fix/<slug>, or docs/<slug>.

Draft using the template below.

Output Format

# Pull Request Draft ## Branch name suggestion git checkout -b <kebab-case, e.g., feat/add-firewall-tools> ## Title <single-line imperative title, e.g., "feat: add firewall management tools"> ## Description <Start with "This pull request adds/fixes/improves ...", explain the change, any behavior changes or considerations. No need to list tests.>

name	pr-draft-summary
description	Generate a PR-ready summary block with branch suggestion, title, and description. Use in the final handoff after moderate-or-larger code changes; skip for trivial or conversation-only tasks.