Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

github-pr-create

Étoiles4

Forks1

Mis à jour26 mai 2026 à 22:04

Creates a GitHub pull request from staged git changes, handling commit, push, and PR creation in one workflow. Activate when the user asks to "create PR", "open pull request", "push and create PR", "submit PR", or wants to send their changes upstream to os-autoinst-distri-opensuse.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

mpagot

mpagot/os-autoinst-distri-opensuse-skills

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	github-pr-create
description	Creates a GitHub pull request from staged git changes, handling commit, push, and PR creation in one workflow. Activate when the user asks to "create PR", "open pull request", "push and create PR", "submit PR", or wants to send their changes upstream to os-autoinst-distri-opensuse.

You help an OSADO developer create a GitHub pull request from staged git changes. This is an end-to-end workflow: commit, push, and PR creation.

Workflow

1. Prepare and execute the commit

Delegate to the git-commit skill to:

Inspect the staged changes
Propose a commit message complying with OSADO CONTRIBUTING.md rules
Write it to commit_message.txt for the user to review
Wait for the user's approval

Once approved, run:

git commit -F commit_message.txt

2. Push the changes

Get the current branch name with git rev-parse --abbrev-ref HEAD.
Push the changes to the remote repository:
```
git push --set-upstream origin <branch>
```

3. Create the pull request

Read the pull request template from .github/PULL_REQUEST_TEMPLATE.md (if it exists in the target repo).
Get the title from the first line of the commit message.
Use the rest of the commit message as the description of the pull request.
Combine the description with the content of the pull request template.
Remove the line about needles if the user does not explicitly request it.
Ask the user for a ticket reference and put it in the description.
Write the PR description to a temporary file (e.g., pr_body.txt).

Create the pull request using the GitHub CLI:

gh pr create \
  --title "<title>" \
  --body-file pr_body.txt \
  --repo https://github.com/os-autoinst/os-autoinst-distri-opensuse

Important Notes

Always use the --repo https://github.com/os-autoinst/os-autoinst-distri-opensuse option to ensure the PR targets the upstream repository, not a fork.
If GitHub MCP tools are available, prefer using them over the gh CLI.
The workflow is interactive: wait for user approval at each critical step (commit message, PR description) before proceeding.

Plus depuis ce dépôt

même dépôt

unit-test-wizard

mpagot/os-autoinst-distri-opensuse-skills

Writes and reviews OSADO Perl unit tests for library modules in lib/. Activate when the user asks to "write a test", "add unit tests", "scaffold a test file", "review this test", "check test quality", or needs help with Test::MockModule, dies_ok assertions, or subtest structure.

2026-05-284

git-commit

mpagot/os-autoinst-distri-opensuse-skills

Helps write OSADO-compliant git commit messages for staged changes. Activate when the user asks to "commit", "write commit message", "prepare commit", "stage and commit", or needs help creating a commit message following OSADO CONTRIBUTING.md rules.

2026-05-264

local-lint-test

mpagot/os-autoinst-distri-opensuse-skills

Recommends the fastest local commands to validate edited OSADO code before pushing. Activate when the user asks "how do I check my code", "what should I run locally", "lint my changes", "does this compile", "run perltidy", "run perlcritic", "run a unit test", "check formatting", or after editing files to verify correctness. Covers compilation, formatting, linting, unit tests, YAML validation, and static analysis -- always preferring the lightest targeted command over full-suite runs.

2026-05-194

test-catalog

mpagot/os-autoinst-distri-opensuse-skills

Add or audit a Perldoc documentation header on an OSADO test module following the test catalog standard. Use when a user asks to "add header", "document", or "add catalog header" to a Perl test module.

2026-05-194

openqa-log-analyzer

mpagot/os-autoinst-distri-opensuse-skills

A specialized skill for analyzing openQA logs — triage failures, measure command timing, detect infrastructure lag, extract command output, and compare runs across multiple log files.

2026-05-114

vr-planner

mpagot/os-autoinst-distri-opensuse-skills

Plans how to verify changes to an os-autoinst-distri-opensuse (OSADO) checkout. Use this skill when the user asks "how do I test my change", "what verification run (VR) should I do", "which openQA job should I clone", or "what's affected by my edit". Determines required unit tests, affected test modules, YAML schedules, and openqa-clone-job commands.

2026-05-064

name	github-pr-create
description	Creates a GitHub pull request from staged git changes, handling commit, push, and PR creation in one workflow. Activate when the user asks to "create PR", "open pull request", "push and create PR", "submit PR", or wants to send their changes upstream to os-autoinst-distri-opensuse.

You help an OSADO developer create a GitHub pull request from staged git changes. This is an end-to-end workflow: commit, push, and PR creation.

Workflow

1. Prepare and execute the commit

Delegate to the git-commit skill to:

Inspect the staged changes
Propose a commit message complying with OSADO CONTRIBUTING.md rules
Write it to commit_message.txt for the user to review
Wait for the user's approval

Once approved, run:

git commit -F commit_message.txt

2. Push the changes

Get the current branch name with git rev-parse --abbrev-ref HEAD.
Push the changes to the remote repository:
```
git push --set-upstream origin <branch>
```

3. Create the pull request

Read the pull request template from .github/PULL_REQUEST_TEMPLATE.md (if it exists in the target repo).
Get the title from the first line of the commit message.
Use the rest of the commit message as the description of the pull request.
Combine the description with the content of the pull request template.
Remove the line about needles if the user does not explicitly request it.
Ask the user for a ticket reference and put it in the description.
Write the PR description to a temporary file (e.g., pr_body.txt).

Create the pull request using the GitHub CLI:

gh pr create \
  --title "<title>" \
  --body-file pr_body.txt \
  --repo https://github.com/os-autoinst/os-autoinst-distri-opensuse

Important Notes

Always use the --repo https://github.com/os-autoinst/os-autoinst-distri-opensuse option to ensure the PR targets the upstream repository, not a fork.
If GitHub MCP tools are available, prefer using them over the gh CLI.
The workflow is interactive: wait for user approval at each critical step (commit message, PR description) before proceeding.