Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

open-pr

Estrelas0

Forks0

Atualizado29 de janeiro de 2026 às 16:34

Open pull requests for the current git repo: verify you are not on main/prod, compare your branch to main, commit any pending work, and create a PR (prefer gh). Use when asked to open or create a PR, draft a PR description, or automate the PR workflow for a local git branch.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

heykvnzhao

heykvnzhao/dotfiles

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	open-pr
description	Open pull requests for the current git repo: verify you are not on main/prod, compare your branch to main, commit any pending work, and create a PR (prefer gh). Use when asked to open or create a PR, draft a PR description, or automate the PR workflow for a local git branch.

Open PR

Overview

Create a pull request from the current branch to main, ensuring the branch is valid, changes are committed, and the PR description follows the required format.

Workflow

1. Verify branch and repo

Always prepend GIT_EDITOR=true to every git command.
Confirm the current branch and ensure it is not main or prod:
- GIT_EDITOR=true git rev-parse --abbrev-ref HEAD
- If branch is main or prod, stop and explain why you cannot proceed.

2. Compare branch against main

Show what will be in the PR relative to main:
- GIT_EDITOR=true git fetch origin main (if origin exists)
- GIT_EDITOR=true git log --oneline main..HEAD
- GIT_EDITOR=true git diff --stat main...HEAD
If main does not exist locally or remotely, stop and ask how to proceed.

3. Commit pending work (if any)

Check for staged/unstaged changes:
- GIT_EDITOR=true git status --porcelain
If there are changes:
- Stage everything relevant: GIT_EDITOR=true git add -A
- Ask the user for a commit message if none was provided.
- Commit: GIT_EDITOR=true git commit -m "<message>"
If there are no changes, proceed.

4. Draft PR title and body

Use this exact format:

<feature_area>: <Title> (80 characters or less)

<TLDR> (no more than 2 sentences)

<Description>
- 1~3 bullet points explaining what's changing

Keep the title line within 80 characters.
Ensure TLDR is at most two sentences.
Provide 1–3 concise bullets.

5. Create the PR (prefer gh)

Check if GitHub CLI is installed: command -v gh.
Ensure the branch is pushed (set upstream if missing):
- GIT_EDITOR=true git push -u origin <branch>
If gh is available, create the PR:
- gh pr create --base main --head <branch> --title "<title>" --body "<body>"
If gh is not available, explain the manual steps to open a PR on the hosting service.

6. Respond with the PR link

Always paste the PR URL in your response so it is clickable.
If needed, fetch it via:
- gh pr view --json url -q .url

Mais deste repositório

mesmo repositório

deslop-writing

heykvnzhao/dotfiles

Clean up AI-generated writing by removing slop (generic tone, filler, inflated claims, vague attributions, list spam) while keeping meaning the same. Use when asked to "humanize" text, remove AI-sounding writing, or align prose with local/author voice.

2026-01-310

writing-best-practices

heykvnzhao/dotfiles

Write and edit in a clear, direct style that avoids AI-sounding artifacts. Use whenever drafting or rewriting prose (docs, READMEs, PR descriptions, issues, blog posts, emails, UI copy) and when aligning to the author's preferred voice.

2026-01-310

deslop-code

heykvnzhao/dotfiles

Clean up AI-generated code changes by reviewing diffs against main and removing stylistic or structural artifacts (over-commenting, unnecessary defensive checks, try/catch noise, any-casts, inconsistent style). Use when asked to “remove AI code slop,” “humanize” changes, or align a branch’s edits with existing codebase conventions.

2026-01-290

agents-md-best-practices

heykvnzhao/dotfiles

Refactor AGENTS.md instructions to follow progressive disclosure and AGENTS.md best practices. Use when asked to audit, reorganize, or split AGENTS.md into a minimal root file plus linked docs; includes contradiction checks, essential extraction, grouping, and deletion flags.

2026-01-290

git-commit-plan

heykvnzhao/dotfiles

Plan commits from the current working tree. Use when asked how to split changes into commits, what to stage together, how to handle untracked files, or to propose commit messages and an execution plan (stage/commit) based on `git status`/diffs.

2026-01-290

coding-best-practices

heykvnzhao/dotfiles

General coding principles for writing clean, maintainable code. Use for development work, code reviews, refactoring, dependency changes, and design discussions about code structure, performance, and reliability.

2026-01-290

name	open-pr
description	Open pull requests for the current git repo: verify you are not on main/prod, compare your branch to main, commit any pending work, and create a PR (prefer gh). Use when asked to open or create a PR, draft a PR description, or automate the PR workflow for a local git branch.

Open PR

Overview

Create a pull request from the current branch to main, ensuring the branch is valid, changes are committed, and the PR description follows the required format.

Workflow

1. Verify branch and repo

Always prepend GIT_EDITOR=true to every git command.
Confirm the current branch and ensure it is not main or prod:
- GIT_EDITOR=true git rev-parse --abbrev-ref HEAD
- If branch is main or prod, stop and explain why you cannot proceed.

2. Compare branch against main

Show what will be in the PR relative to main:
- GIT_EDITOR=true git fetch origin main (if origin exists)
- GIT_EDITOR=true git log --oneline main..HEAD
- GIT_EDITOR=true git diff --stat main...HEAD
If main does not exist locally or remotely, stop and ask how to proceed.

3. Commit pending work (if any)

Check for staged/unstaged changes:
- GIT_EDITOR=true git status --porcelain
If there are changes:
- Stage everything relevant: GIT_EDITOR=true git add -A
- Ask the user for a commit message if none was provided.
- Commit: GIT_EDITOR=true git commit -m "<message>"
If there are no changes, proceed.

4. Draft PR title and body

Use this exact format:

<feature_area>: <Title> (80 characters or less)

<TLDR> (no more than 2 sentences)

<Description>
- 1~3 bullet points explaining what's changing

Keep the title line within 80 characters.
Ensure TLDR is at most two sentences.
Provide 1–3 concise bullets.

5. Create the PR (prefer gh)

Check if GitHub CLI is installed: command -v gh.
Ensure the branch is pushed (set upstream if missing):
- GIT_EDITOR=true git push -u origin <branch>
If gh is available, create the PR:
- gh pr create --base main --head <branch> --title "<title>" --body "<body>"
If gh is not available, explain the manual steps to open a PR on the hosting service.

6. Respond with the PR link

Always paste the PR URL in your response so it is clickable.
If needed, fetch it via:
- gh pr view --json url -q .url