القائمة
Cherry-pick a commit from main to a Sui release branch, create the release PR, and report the PR URL.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/MystenLabs/sui --skill cherry-pickيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Prepare, validate, and send or update a pull request with full due diligence
Use when reading or reasoning about compiled Move bytecode or `sui move disassemble` output. Mental model for the binary format, what survives compilation (and what's lost), and how to read disassembly soundly. Trigger on "what does this package do?", "read this .mv module", "interpret this disassembly", or whenever an analysis needs to interpret bytecode faithfully.
Pointer to the official Mysten Labs skills for building on Sui — language fundamentals, object model, PTBs, SDKs, publishing, upgrades, frontend integration, accessing on-chain data. Maintained upstream at github.com/MystenLabs/skills; pinned to the same ref the audit catalog derives from (see maintenance/UPSTREAMS.md). Trigger on "build a contract", "publish a package", "upgrade a module or package", "use the TypeScript SDK", "write a PTB", "set up a Sui client".
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | cherry-pick |
| description | Cherry-pick a commit from main to a Sui release branch, create the release PR, and report the PR URL. |
Cherry-picks a commit from main to a release branch and creates a PR.
/cherry-pick <commit-sha> <release-version>
Example: /cherry-pick abc123 1.64
$ARGUMENTS should contain two space-separated values:
Parse the arguments to extract the commit SHA and release version. If arguments are missing or unclear, ask the user for clarification.
Execute the following steps:
git show --oneline --no-patch <commit-sha>
Save the commit message for use in the PR title.
The release branch naming convention is releases/sui-v<version>.0-release.
git fetch origin releases/sui-v<version>.0-release
git checkout releases/sui-v<version>.0-release
git cherry-pick <commit-sha>
If there are conflicts:
git cherry-pick --continueUse the naming convention cherry-pick-<short-sha>-to-<version>:
git checkout -b cherry-pick-<short-sha>-to-<version>
git push -u origin cherry-pick-<short-sha>-to-<version>
Create a PR targeting the release branch:
gh pr create --base releases/sui-v<version>.0-release \
--title "[<version>] <original-commit-message>" \
--body "## Summary
Cherry-pick of <original-pr-link-if-available> to the <version> release branch.
Original commit: <full-commit-sha>"
git checkout main