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

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

open-regeneration-pr

Étoiles2 297

Forks1 379

Mis à jour29 mai 2026 à 22:53

Commit ai-projects regeneration output to a new branch and open a draft GitHub PR against Azure/azure-sdk-for-js main. Use when the prior five regen skills are complete and you need to push the branch and create a draft pull request via the gh CLI. Stages five logical commits (emitter output, post-emitter edits, samples, tests, changelog). Never force-pushes; always opens as draft.

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

Azure

Azure/azure-sdk-for-js

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	open-regeneration-pr
description	Commit ai-projects regeneration output to a new branch and open a draft GitHub PR against Azure/azure-sdk-for-js main. Use when the prior five regen skills are complete and you need to push the branch and create a draft pull request via the gh CLI. Stages five logical commits (emitter output, post-emitter edits, samples, tests, changelog). Never force-pushes; always opens as draft.

Open the regeneration PR for ai-projects

When to Use

The previous five skills (regenerate-from-typespec, apply-post-emitter-edits, author-samples, author-tests, update-changelog) have all completed.
The working tree has staged-able changes only in sdk/ai/ai-projects/.
You're ready to publish a draft PR for human review.

Inputs

Name	Default	Description
`tspCommit`	required	The 40-char SHA from `tsp-location.saved.yaml` (the upstream commit being pulled in).
`branchName`	`regen/ai-projects/<short-sha>-<yyyyMMdd>`	Branch name to create.
`remote`	`origin`	Git remote to push to.

Prerequisites

gh CLI installed and authenticated against Azure/azure-sdk-for-js.
Clean working tree apart from changes under sdk/ai/ai-projects/.

Procedure

Run from sdk/ai/ai-projects/ (the script cds to the repo root as needed).

Step 1: Create branch and stage commits

./.github/skills/open-regeneration-pr/scripts/open-pr.ps1 -TspCommit <40-char-sha>

The script (scripts/open-pr.ps1) does:

Aborts if there are unstaged changes outside sdk/ai/ai-projects/.
Creates branch regen/ai-projects/<short-sha>-<yyyyMMdd> from current HEAD.
Stages five logical commits, each scoped via path filters:
- [ai-projects] regen: emitter output @ <short-sha> — generated/, tsp-location.saved.yaml.
- [ai-projects] regen: post-emitter edits — src/ (excluding samples/tests).
- [ai-projects] regen: samples for new features — samples-dev/.
- [ai-projects] regen: tests for new GA features — test/.
- [ai-projects] regen: changelog — CHANGELOG.md.
Pushes to origin (no force).
Calls gh pr create --draft with title [ai-projects] Regenerate from azure-rest-api-specs@<short-sha> and a body templated from changelog content + a verification checklist.

Step 2: Verify

The PR shows up as Draft in GitHub.
The PR body links the upstream commit: https://github.com/Azure/azure-rest-api-specs/commit/<sha>.
The verification checklist (build, format, test:node, build:samples) is present and unchecked, awaiting human/CI confirmation.

Safety rails

Never runs git push --force or git push --force-with-lease.
Never opens a non-draft PR — humans flip it to "ready for review".
Never stages files outside sdk/ai/ai-projects/.
Aborts immediately if a commit step would be empty (signals an upstream skill failure).

Plus depuis ce dépôt

même dépôt

agentic-workflows

Azure/azure-sdk-for-js

Route gh-aw workflow design/create/debug/upgrade requests to the right prompts.

2026-07-082.3k

rerecord-tests

Azure/azure-sdk-for-js

Re-record the ai-projects live test suite, push only the recordings whose playback passes to the Azure/azure-sdk-assets repo, and open a PR for the updated assets.json. Use when test recordings are stale, a recorded test fails in playback in CI, or new recorded tests need fresh recordings. Wraps TEST_MODE=record / TEST_MODE=playback runs, dev-tool test-proxy push, and a single-file assets.json PR via the gh CLI.

2026-06-292.3k

node-migration

Azure/azure-sdk-for-js

Migrate Azure/azure-sdk-for-js to a user-specified minimum Node.js version while preserving any existing references above the target.

2026-06-232.3k

sdk-workflow

Azure/azure-sdk-for-js

**UTILITY SKILL** — Must be consulted for SDK development workflow tasks. Routes agents to the correct tools and documentation for building, testing, linting, formatting, provisioning, deploying, and other package development tasks. WHEN: "build package", "run tests", "lint code", "format code", "run checks", "prepare samples", "publish samples", "apply customization", "run migrations", "bump version", "extract API", "update snippets", "check API compatibility", "manage test recordings", "provision test resources", "deploy test resources", "create test resources", "set up test environment", "authenticate to Azure", "login to Azure", "release package", "increment version", "troubleshoot CI", "fix CI failure", "CredScan", "credential scan", "push recordings", "asset sync", "update recordings".

2026-06-192.3k

cu-sdk-common-knowledge

Azure/azure-sdk-for-js

Domain knowledge for Azure AI Content Understanding. Use this skill to answer questions about Content Understanding concepts, analyzers, field schemas, API operations, and JavaScript SDK usage. Always consult official documentation before answering.

2026-06-112.3k

cu-sdk-sample-run

Azure/azure-sdk-for-js

Run a specific sample for the Azure AI Content Understanding JavaScript SDK. Use when users want to run a particular sample like analyzeUrl.js or analyzeInvoice.js.

2026-06-112.3k

name	open-regeneration-pr
description	Commit ai-projects regeneration output to a new branch and open a draft GitHub PR against Azure/azure-sdk-for-js main. Use when the prior five regen skills are complete and you need to push the branch and create a draft pull request via the gh CLI. Stages five logical commits (emitter output, post-emitter edits, samples, tests, changelog). Never force-pushes; always opens as draft.

Open the regeneration PR for ai-projects

When to Use

The previous five skills (regenerate-from-typespec, apply-post-emitter-edits, author-samples, author-tests, update-changelog) have all completed.
The working tree has staged-able changes only in sdk/ai/ai-projects/.
You're ready to publish a draft PR for human review.

Inputs

Name	Default	Description
`tspCommit`	required	The 40-char SHA from `tsp-location.saved.yaml` (the upstream commit being pulled in).
`branchName`	`regen/ai-projects/<short-sha>-<yyyyMMdd>`	Branch name to create.
`remote`	`origin`	Git remote to push to.

Prerequisites

gh CLI installed and authenticated against Azure/azure-sdk-for-js.
Clean working tree apart from changes under sdk/ai/ai-projects/.

Procedure

Run from sdk/ai/ai-projects/ (the script cds to the repo root as needed).

Step 1: Create branch and stage commits

./.github/skills/open-regeneration-pr/scripts/open-pr.ps1 -TspCommit <40-char-sha>

The script (scripts/open-pr.ps1) does:

Aborts if there are unstaged changes outside sdk/ai/ai-projects/.
Creates branch regen/ai-projects/<short-sha>-<yyyyMMdd> from current HEAD.
Stages five logical commits, each scoped via path filters:
- [ai-projects] regen: emitter output @ <short-sha> — generated/, tsp-location.saved.yaml.
- [ai-projects] regen: post-emitter edits — src/ (excluding samples/tests).
- [ai-projects] regen: samples for new features — samples-dev/.
- [ai-projects] regen: tests for new GA features — test/.
- [ai-projects] regen: changelog — CHANGELOG.md.
Pushes to origin (no force).
Calls gh pr create --draft with title [ai-projects] Regenerate from azure-rest-api-specs@<short-sha> and a body templated from changelog content + a verification checklist.

Step 2: Verify

The PR shows up as Draft in GitHub.
The PR body links the upstream commit: https://github.com/Azure/azure-rest-api-specs/commit/<sha>.
The verification checklist (build, format, test:node, build:samples) is present and unchecked, awaiting human/CI confirmation.

Safety rails

Never runs git push --force or git push --force-with-lease.
Never opens a non-draft PR — humans flip it to "ready for review".
Never stages files outside sdk/ai/ai-projects/.
Aborts immediately if a commit step would be empty (signals an upstream skill failure).