mcpbeat

Open Regeneration Pr

azure/open-regeneration-pr

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.

2k tokens
context cost
the whole folder, loaded on every use
2
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
2294
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/Azure/azure-sdk-for-js --skill open-regeneration-pr

What comes with it

6 408 bytes besides the instruction
scripts/open-pr.ps1

The instruction itself

8 sections, as written by the author

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).

How to use it

Copy the folder

Take azure/open-regeneration-pr from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.