تشغيل أي مهارة في Manus بنقرة واحدة

ابدأ الآن

pr-create

النجوم٥

التفرعات٢

آخر تحديث١٩ أبريل ٢٠٢٦ في ١٩:٠٠

Open a pull request for the current branch using the repo's PR template

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

jordanleven

jordanleven/nedryland

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

SKILL.md

readonly

name	pr-create
description	Open a pull request for the current branch using the repo's PR template
disable-model-invocation	true

Open a pull request for the current branch.

Steps

Check for a PR template by looking for:
- .github/pull_request_template.md
- .github/PULL_REQUEST_TEMPLATE.md
- .github/PULL_REQUEST_TEMPLATE/*.md (multiple templates)
Determine the PR title from the branch's commits:
- If the branch has a single commit, derive the title from its subject line
- If the branch has multiple commits, write a title that summarizes the overall change
- Use Title Case — no commit type prefix (no feat:, chore:, etc.)
- Be succinct: describe what the PR does, not how it does it
Fill out the PR body:
- If a template exists, fill out every section in full — do not delete sections, leave placeholders, or write "N/A" without explanation. Read the commits and diff to answer each section with real content.
- If no template exists, write a body that covers: what changed, why, and how to verify it.

Open the PR with gh pr create:

gh pr create --title "<title>" --body "<body>"

Output the PR URL so the user can review it.

Rules

Never skip template sections. If a section asks for a test plan, write one based on what actually changed. If it asks for context, provide it from the commits.
The body should be written for a reviewer who has no prior context — assume they are coming in cold.

المزيد من هذا المستودع

نفس المستودع

force-refresh-support

jordanleven/nedryland

Review open Force Refresh support requests, assess their status, and draft replies

2026-05-025

commit

jordanleven/nedryland

Stage and commit changes using project conventions

2026-04-195

curate-commits

jordanleven/nedryland

Curate the commit history of the current branch — either as a reviewer-friendly narrative or collapsed into clean atomic commits ready for main

2026-04-195

dependabot-rebase

jordanleven/nedryland

Trigger a rebase on all open Dependabot pull requests

2026-04-195

update-deps

jordanleven/nedryland

Update dependencies for the project in the current working directory

2026-04-195

name	pr-create
description	Open a pull request for the current branch using the repo's PR template
disable-model-invocation	true

Open a pull request for the current branch.

Steps

Check for a PR template by looking for:
- .github/pull_request_template.md
- .github/PULL_REQUEST_TEMPLATE.md
- .github/PULL_REQUEST_TEMPLATE/*.md (multiple templates)
Determine the PR title from the branch's commits:
- If the branch has a single commit, derive the title from its subject line
- If the branch has multiple commits, write a title that summarizes the overall change
- Use Title Case — no commit type prefix (no feat:, chore:, etc.)
- Be succinct: describe what the PR does, not how it does it
Fill out the PR body:
- If a template exists, fill out every section in full — do not delete sections, leave placeholders, or write "N/A" without explanation. Read the commits and diff to answer each section with real content.
- If no template exists, write a body that covers: what changed, why, and how to verify it.

Open the PR with gh pr create:

gh pr create --title "<title>" --body "<body>"

Output the PR URL so the user can review it.

Rules

Never skip template sections. If a section asks for a test plan, write one based on what actually changed. If it asks for context, provide it from the commits.
The body should be written for a reviewer who has no prior context — assume they are coming in cold.