Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

git-pr

Sterne4

Forks0

Aktualisiert11. Juli 2026 um 09:57

Use this skill to generate and apply a clear title and structured description for a GitHub Pull Request by deep-investigating all changed files. Use it when the user opens a new PR, when a PR's title or description is missing or stale, or when the user says "update this PR", "describe this PR", or "write a summary for this PR." Applies the result directly via gh pr edit.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

cuozg

cuozg/oh-my-skills

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

Datei-Explorer

2 Dateien

SKILL.md

readonly

name	git-pr
description	Use this skill to generate and apply a clear title and structured description for a GitHub Pull Request by deep-investigating all changed files. Use it when the user opens a new PR, when a PR's title or description is missing or stale, or when the user says "update this PR", "describe this PR", or "write a summary for this PR." Applies the result directly via gh pr edit.
metadata	{"author":"kuozg","version":"1.0"}

git-pr

Deep-investigate all files changed in a PR, then generate and apply a reviewer-ready title and structured description via gh pr edit.

When to Use

Opening/Create a new PR that needs a clear title and description
Updating a stale or missing PR title or description before review
Generating documentation-quality PR context for reviewers
Automating PR metadata from a feature branch

Workflow

Fetch — Run gh pr diff or git diff base...HEAD to get the full PR diff
Read — Read every changed file to understand the actual implementation
Investigate — Trace cross-file dependencies, identify the root change vs cascading effects
Draft title — Write a concise PR title in imperative or descriptive form that reflects the root change
Draft body — Write a structured description using the template in references/pr-description-template.md
Apply — Run gh pr edit --title "..." --body "..." to push both fields to GitHub

Rules

Read all changed files — do not summarize from diff hunks alone
Separate what changed from why it changed in the description
Keep the title specific, concise, and aligned with the actual implementation
Include testing instructions that a reviewer can actually follow
Never fabricate behavior — only describe what the code does
Apply via gh pr edit --title --body — do not just print the title or description

Output Format

Title and description applied to the GitHub PR via gh pr edit --title --body. Body sections MUST follow the repository PR template. (MANDATORY, NO NEGOTIATE)

Reference Files

references/pr-description-template.md — PR body structure with checklist, summary, changes, testing, links, screenshots, and notes

Load references on demand via read_skill_file("git-pr", "references/{file}").

Mehr aus diesem Repository

gleiches Repository

git-rebase

cuozg/oh-my-skills

Use when rebasing current branch onto a target branch, especially when the working tree has uncommitted changes, the local target ref may be behind its remote, or the rebase risks conflicts that need user review.

2026-07-114

goal-detail

cuozg/oh-my-skills

Expand a goal-create file into a detailed, implementation-ready task breakdown. Use when a user has a goal under Docs/Goals and wants it expanded into per-Task blocks (files, interfaces, code snippets, bash commands, acceptance criteria) ready to hand to goal-execute. Triggers: "detail this goal", "expand the goal", "break the goal into tasks", "create task breakdown", "plan the goal", "write implementation steps for this goal", "make an epic-style plan from this goal". Do not use for executing the goal, writing test cases, or verifying completed work.

2026-07-094

unity-data-struct

cuozg/oh-my-skills

Generate tree-format data structure documentation for Unity JSON schemas (db_*.json tables like db_TTE, db_DBSE). Use when the user pastes/shares a table of fields with short keys (a0, b1, c2...), wants a hierarchical tree diagram of a JSON data structure, asks to "create tree format", "data structure doc", "document db_XXX.json", or "generate data struct markdown". Output is a markdown file with a tree showing parent-child nesting (Object arrays → child objects) plus per-level field reference tables.

2026-07-084

unity-standards

cuozg/oh-my-skills

Use for Unity engineering standards: C# code, asset managers, Addressables, analytics, LiveOps, config, server API, IAP, prefab, Canvas UI, material, shader, draw calls, batching, debugging, optimization, reviews, project investigation, tests, plans, todos, acceptance criteria, and technical docs.

2026-07-084

unity-debug

cuozg/oh-my-skills

Diagnose Unity bugs from compile errors to stack traces, runtime failures, and tricky logic issues; gather reproduction details, trace the code path, prove the root cause with evidence, and report options without changing code unless asked.

2026-06-244

unity-solution

cuozg/oh-my-skills

Use when the user provides a Unity requirement, goal, feature idea, or bug objective — with or without a proposed solution or technical approach. Detects whether the user supplied a solution or only a goal, then either designs a Unity solution (tech approach, risks, concerns, options) or evaluates the supplied solution against Unity standards and project context. Triggers: "design a solution", "evaluate this approach", "review my solution", "find a technical approach", "is this solution good", "solution for", "tech approach for", "how should we build/fix this".

2026-06-244

name	git-pr
description	Use this skill to generate and apply a clear title and structured description for a GitHub Pull Request by deep-investigating all changed files. Use it when the user opens a new PR, when a PR's title or description is missing or stale, or when the user says "update this PR", "describe this PR", or "write a summary for this PR." Applies the result directly via gh pr edit.
metadata	{"author":"kuozg","version":"1.0"}

git-pr

Deep-investigate all files changed in a PR, then generate and apply a reviewer-ready title and structured description via gh pr edit.

When to Use

Opening/Create a new PR that needs a clear title and description
Updating a stale or missing PR title or description before review
Generating documentation-quality PR context for reviewers
Automating PR metadata from a feature branch

Workflow

Fetch — Run gh pr diff or git diff base...HEAD to get the full PR diff
Read — Read every changed file to understand the actual implementation
Investigate — Trace cross-file dependencies, identify the root change vs cascading effects
Draft title — Write a concise PR title in imperative or descriptive form that reflects the root change
Draft body — Write a structured description using the template in references/pr-description-template.md
Apply — Run gh pr edit --title "..." --body "..." to push both fields to GitHub

Rules

Read all changed files — do not summarize from diff hunks alone
Separate what changed from why it changed in the description
Keep the title specific, concise, and aligned with the actual implementation
Include testing instructions that a reviewer can actually follow
Never fabricate behavior — only describe what the code does
Apply via gh pr edit --title --body — do not just print the title or description

Output Format

Title and description applied to the GitHub PR via gh pr edit --title --body. Body sections MUST follow the repository PR template. (MANDATORY, NO NEGOTIATE)

Reference Files

references/pr-description-template.md — PR body structure with checklist, summary, changes, testing, links, screenshots, and notes

Load references on demand via read_skill_file("git-pr", "references/{file}").