Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

pr-guidelines

Push branches and open pull requests with correct title/body conventions. Use when preparing a branch for review, writing PR metadata, or opening a PR with linked issues.

In Manus ausführen

Überblick

Push branches and open pull requests with correct title/body conventions. Use when preparing a branch for review, writing PR metadata, or opening a PR with linked issues.

Installationsbefehl

npx skills add https://github.com/minusfive/dot --skill pr-guidelines

Kopieren Sie diesen Befehl und fügen Sie ihn in Claude Code ein, um den Skill zu installieren

Quelle

minusfive/dot

Sterne5

Forks0

Aktualisiert3. Juni 2026 um 01:56

SKILL.md

readonly

name	pr-guidelines
description	Push branches and open pull requests with correct title/body conventions. Use when preparing a branch for review, writing PR metadata, or opening a PR with linked issues.

Pull Request Guidelines

Complete commit-guidelines skill (including hook policy, branch creation, and commits) before proceeding

1: Push

Push the branch to the remote repository
Verify the push succeeded before opening a pull request

2: Pull Request

PR title and message formatting MUST follow the same guidelines as commits
The pull request body should include a brief summary of the changes and any relevant context or notes for the reviewer
MUST NOT include commit messages in the pull request body — these are clear from the PR's commit history and will quickly become stale
Reference any related issues or pull requests where relevant
Request explicit approval before opening the pull request, never auto-open without user confirmation

Mehr aus diesem Repository

gleiches Repository

agent-instructions-authoring

minusfive/dot

Author, audit, and modify agent instructions and rule entrypoints — skills, AGENTS.md, CLAUDE.md, subagent/agent definitions, and any other file that instructs agent behavior. Use when creating, editing, renaming, or reviewing such files; when consolidating duplicated rules across them; or when validating skill metadata, discoverability, and structure.

2026-06-035

coding-guidelines

minusfive/dot

Apply repository coding standards for implementation and review tasks. Use when adding features, fixing bugs, refactoring, updating tests, or resolving lint/type/build issues.

2026-06-035

planning

minusfive/dot

Produce execution-ready implementation plans for complex work. Use when tasks are multi-step, high-risk, ambiguous, or span multiple files/services.

2026-06-035

commit-guidelines

minusfive/dot

Create branches and commits from local diffs with correct commit message conventions. Use when asked to branch, split commits, write commit messages, or apply commitlint/Conventional Commits rules.

2026-06-035

github-cli

minusfive/dot

Use gh CLI for GitHub operations. Invoke when working with pull requests, issues, workflow runs, releases, repository metadata, or file content on GitHub.

2026-06-035

project-overview

minusfive/dot

Discover project structure, architecture, and tooling before implementation. Use when starting work in an unfamiliar repository or before making non-trivial code changes.

2026-06-035

Quelle

minusfive

minusfive/dot

GitHub-Repository öffnen Creator-Repositorys ansehen

Installationsbefehl

Download

In Manus ausführen

name	pr-guidelines
description	Push branches and open pull requests with correct title/body conventions. Use when preparing a branch for review, writing PR metadata, or opening a PR with linked issues.

Pull Request Guidelines

Complete commit-guidelines skill (including hook policy, branch creation, and commits) before proceeding

1: Push

Push the branch to the remote repository
Verify the push succeeded before opening a pull request

2: Pull Request

PR title and message formatting MUST follow the same guidelines as commits
The pull request body should include a brief summary of the changes and any relevant context or notes for the reviewer
MUST NOT include commit messages in the pull request body — these are clear from the PR's commit history and will quickly become stale
Reference any related issues or pull requests where relevant
Request explicit approval before opening the pull request, never auto-open without user confirmation