菜单
Update release notes based on the latest changes from the current branch. Use when: "update release notes", "add to release notes", "write release notes", "document changes in release notes", "sync release notes with branch".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use CLI for Microsoft 365 (`m365`) to manage Microsoft 365 tenants, SharePoint, Entra ID, Teams, Outlook, Planner, Power Platform, Viva, Purview, and more from the command line. Activate when the user asks to manage, query, configure, or automate anything in Microsoft 365 — including SharePoint sites/lists/pages, Entra users/groups/apps, Teams channels/messages, Outlook mail/calendars, Planner tasks, Power Automate flows, Power Apps, Viva Engage/Connections, Purview labels, OneDrive, To Do, or Microsoft Graph extensions.
This skill should be used when the user asks to "review a PR", "check this pull request", "PR review", "review pull request", "check PR against checklist", or needs to review a pull request against the project's PR checklist and coding standards.
This skill should be used when the user asks to "build a new command", "create a command", "implement a command", "add a new CLI command", or needs to build a new command for CLI for Microsoft 365 from a GitHub issue spec. It covers the full workflow: command logic, unit tests, documentation, sidebar registration, and PR checklist verification.
Regenerate the clim365 skill's command index after adding, removing, or renaming CLI for Microsoft 365 commands. Use when asked to "refresh the clim365 skill", "update the command index", "regenerate commands.txt", or after shipping a new command.
This skill should be used when the user asks to "patch vulnerabilities", "fix npm audit issues", "update vulnerable dependencies", "update outdated dependencies", "scan and fix vulnerabilities", "run npm audit and patch", "fix security vulnerabilities", "update npm packages", "check for outdated packages", or needs to comprehensively scan, patch, and re-verify npm dependencies with a cooldown safety check. Covers three blind spots: npm audit (security), npm outdated (staleness), and override checks.
Migrate CLI for Microsoft 365 commands from legacy initOptions/initValidators/initTelemetry pattern to Zod schema validation. Use when asked to "migrate to zod", "upgrade command to zod", "convert command validation to zod", or when working on commands that still use the old pattern.
| name | update-release-notes |
| description | Update release notes based on the latest changes from the current branch. Use when: "update release notes", "add to release notes", "write release notes", "document changes in release notes", "sync release notes with branch". |
| disable-model-invocation | true |
Update docs/docs/about/release-notes.mdx based on the changes in the current branch compared to main.
Run:
Get commit hash of latest release notes update
git log --grep="Updates release notes" -n 1 --format="%H"
Use the commit hash
git log <commit_hash>..HEAD --oneline --no-decorate
If the branch has no commits ahead of main, inform the user and stop.
For each commit, extract:
Closes #NNN or #NNN in the message)Read docs/docs/about/release-notes.mdx to find the current unreleased version section at the top of the file. The unreleased version heading looks like ## vX.Y.Z (no link), while released versions have links: ## [vX.Y.Z](url).
If there is no unreleased version section (the first heading is a released version with a link), inform the user and stop. Do not create new version headings.
Classify each commit into one of these categories based on the commit message:
| Commit message pattern | Category |
|---|---|
Starts with Adds '...' command | New command |
Starts with Fixes | Change (fix) |
Starts with Extends, Enhances | Change (enhancement) |
Starts with Migrates | Change (migration) |
| Everything else (updates, removes, adds support, etc.) | Change (other) |
For each new command, determine:
spo site list)spo → SharePointspe → SharePoint Embeddedspp → SharePoint Premiumentra → Entra IDteams → Teamsoutlook → Outlookviva → Vivaexternal → Externalflow → Flowpa → Power Appspp → Power Platformplanner → Plannerpurview → Purviewbooking → Bookingonedrive → OneDrive.mdx file under docs/docs/cmd/ using the command name segments- [command name](../cmd/<workload>/<subgroup>/command.mdx) - description [#issue](https://github.com/pnp/cli-microsoft365/issues/issue)
spo site list)issues/ for issues, pull/ for PRs- verb-past-tense description [#issue](https://github.com/pnp/cli-microsoft365/issues/issue)
Use past tense for the verb:
Adds → addedFixes → fixedExtends/Enhances → enhancedMigrates → migratedUpdates → updatedRemoves → removedWhen the change relates to a specific command, link to its doc page inline:
- fixed [command name](../cmd/path.mdx) command [#issue](url)
Insert entries into the current unreleased version section (the first ## vX.Y.Z heading without a link).
### New commands section exists, add entries there**SharePoint:**, **Outlook:**, etc.)### Changes section exists, add entries there### New commands (or after the version heading if there are no new commands)After editing, read back the modified section to verify:
../cmd/...)