Agent skill

Spfx Release

Automate SPFx version releases - branch, update files, commit, open PR, then tag after merge

Install Spfx Release

skills CLI

$ npx skills add pnp/docker-spfx --skill spfx-release -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install pnp/docker-spfx spfx-release --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/pnp/docker-spfx.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/spfx-release .claude/skills/spfx-release && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "spfx-release" agent skill from https://github.com/pnp/docker-spfx/tree/main/.claude/skills/spfx-release into .claude/skills/spfx-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spfx-release", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/pnp/docker-spfx/tree/main/.claude/skills/spfx-release

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add pnp/docker-spfx --skill spfx-release -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install pnp/docker-spfx spfx-release --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pnp/docker-spfx.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/spfx-release .agents/skills/spfx-release && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "spfx-release" agent skill from https://github.com/pnp/docker-spfx/tree/main/.claude/skills/spfx-release into .agents/skills/spfx-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spfx-release", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add pnp/docker-spfx --skill spfx-release -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install pnp/docker-spfx spfx-release --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pnp/docker-spfx.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/spfx-release .cursor/skills/spfx-release && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "spfx-release" agent skill from https://github.com/pnp/docker-spfx/tree/main/.claude/skills/spfx-release into .cursor/skills/spfx-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spfx-release", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/pnp/docker-spfx.git --path .claude/skills/spfx-release

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add pnp/docker-spfx --skill spfx-release -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install pnp/docker-spfx spfx-release --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pnp/docker-spfx.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/spfx-release .gemini/skills/spfx-release && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "spfx-release" agent skill from https://github.com/pnp/docker-spfx/tree/main/.claude/skills/spfx-release into .gemini/skills/spfx-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spfx-release", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install pnp/docker-spfx spfx-release

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add pnp/docker-spfx --skill spfx-release -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/pnp/docker-spfx.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/spfx-release .github/skills/spfx-release && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "spfx-release" agent skill from https://github.com/pnp/docker-spfx/tree/main/.claude/skills/spfx-release into .github/skills/spfx-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spfx-release", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add pnp/docker-spfx --skill spfx-release -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install pnp/docker-spfx spfx-release --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pnp/docker-spfx.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/spfx-release .opencode/skills/spfx-release && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "spfx-release" agent skill from https://github.com/pnp/docker-spfx/tree/main/.claude/skills/spfx-release into .opencode/skills/spfx-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spfx-release", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: spfx-release
GitHub stars: 134
Token cost: ~572 tokens
SKILL.md length: 259 words
Files: 1
Skills in repo: 1
Repo updated: Jul 3, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Automate SPFx version releases - branch, update files, commit, open PR, then tag after merge

Works in 3 steps: Working tree is clean (git status). If… → The new version is not already present… → The tag v$ARGUMENTS does not already…
Tasks that involve Cloud office suites
SKILL.md covers Pre-flight checks and Steps to perform
Calls git and gh

What it does

Spfx Release is an agent skill from pnp/docker-spfx. Automate SPFx version releases - branch, update files, commit, open PR, then tag after merge

Its SKILL.md is about 570 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Documents & Office, covering Cloud office suites and Containers. It works with Microsoft 365, Docker, Microsoft SharePoint and Git. The repository describes itself as: Docker images for working with SharePoint Framework. The licence is MIT.

When your agent uses it

Tasks that involve Cloud office suites
Tasks that involve Containers

Example prompts

“/spfx-release”

Requirements

Pre-approved tools (allowed-tools): Bash, Read, Edit, Grep

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

Working tree is clean (git status). If there are unrelated uncommitted changes, stop and ask the user how to handle them.
The new version is not already present in Dockerfile, README.md, or DevelopmentContainers.md — if it is, the release may already be in…
The tag v$ARGUMENTS does not already exist locally or on origin (git tag --list, git ls-remote --tags origin).

What it can do on your machine

Read from SKILL.md and the folder at commit c4e456f. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Bash
- Read
- Edit
- Grep
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- git
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Spfx Release loads about 572 tokens when it runs. Until then it costs about 26 tokens; SKILL.md has 259 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~26
When it runs · the whole SKILL.md, loaded when a task matches: ~572

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
```
allowed-tools: Bash, Read, Edit, Grep
```

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Download SKILL.mdSave it as .claude/skills/spfx-release/SKILL.md (or your agent's skills folder).

name: spfx-release
description: Automate SPFx version releases - branch, update files, commit, open PR, then tag after merge
allowed-tools: Bash, Read, Edit, Grep
disable-model-invocation: false
argument-hint: [version]

SPFx Release Automation

Release a new SPFx version. The version argument is: $ARGUMENTS

Pre-flight checks

Before making changes, verify:

Working tree is clean (git status). If there are unrelated uncommitted changes, stop and ask the user how to handle them.
The new version is not already present in Dockerfile, README.md, or DevelopmentContainers.md — if it is, the release may already be in flight; surface this and ask before continuing.
The tag v$ARGUMENTS does not already exist locally or on origin (git tag --list, git ls-remote --tags origin).

Steps to perform

Create a release branch from the latest main:
```
git checkout main && git pull
git checkout -b release/v$ARGUMENTS
```
Branch name must be valid git (no spaces, no colons).
Update version in all files — find and replace the old version with $ARGUMENTS in:
- Dockerfile (generator-sharepoint version)
- README.md (Available tags section — update latest, online, and add the new version row)
- DevelopmentContainers.md (devcontainer.json example)
- Run grep -rn "<old-version>" to catch any other references.
Commit changes with message: SPFx v$ARGUMENTS - new version updates
Squash commits on the release branch (release branch only — never on main, since unrelated commits between the last tag and HEAD would get folded in):
- Get the last tag: git describe --tags --abbrev=0
- Soft reset to that tag: git reset --soft <last-tag>
- Re-commit with the same message.

Push the branch and open a PR (confirm with user first):

git push -u origin release/v$ARGUMENTS
gh pr create --title "feat: new SPFx version v$ARGUMENTS" --body "..."

After the PR merges, create and push the tag against the merged commit on main:
```
git checkout main && git pull
git tag v$ARGUMENTS
git push origin v$ARGUMENTS
```
Confirm with the user before pushing the tag.

Always confirm with the user before any push or PR creation.

Files

Just SKILL.md in .claude/skills/spfx-release of pnp/docker-spfx.

Open the folder on GitHubat commit c4e456f

Compare with similar skills

Spfx Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Spfx Release compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Spfx Release this skillpnp/docker-spfx	134	—	~572	Automated safety check: Notes	MIT	3 mo ago
Local Vscuse ValidationOfficeDev/microsoft-365-agents-toolkit	781	—	~10k	Automated safety check: Warn	Custom licence	today
Sap Btp Build Work Zone Advancedsecondsky/sap-skills	462	—	~3.3k	Automated safety check: Pass	GPL-3.0	3 days ago
CLI Microsoft365pnp/cli-microsoft365-mcp-server	131	—	~3.5k	Automated safety check: Pass	MIT	3 days ago
CLI Microsoft365 Scriptpnp/cli-microsoft365-mcp-server	131	—	~3.3k	Automated safety check: Pass	MIT	3 days ago
Slack To Teamsmicrosoft/work-iq	1k	1 repos	~2.3k	Automated safety check: Pass	Custom licence	yesterday

Similar skills

Local Vscuse Validation
OfficeDev/microsoft-365-agents-toolkit
A skill your agent uses when: setting up shared local vscuse prerequisites, credentials, runner, local or pinned published Docker images, local VSIX, env variables, and common rules for Microsoft…
781 GitHub stars~10k tokensUpdated today
Documents & OfficeAuto-check: warnings
Sap Btp Build Work Zone Advanced
secondsky/sap-skills
Develops and administers SAP Build Work Zone, advanced edition digital workplace solutions.
462 GitHub stars~3.3k tokensUpdated 3 days ago
Backend & APIsAuto-check passed
CLI Microsoft365
pnp/cli-microsoft365-mcp-server
Use CLI for Microsoft 365 to manage Microsoft 365 tenants from the terminal.
131 GitHub stars~3.5k tokensUpdated 3 days ago
Documents & OfficeAuto-check passed
CLI Microsoft365 Script
pnp/cli-microsoft365-mcp-server
Write PowerShell scripts using CLI for Microsoft 365 commands to automate Microsoft 365 management tasks.
131 GitHub stars~3.3k tokensUpdated 3 days ago
Documents & OfficeAuto-check passed
Slack To Teams
microsoft/work-iq
Official
Sub-skill of microsoft-365-agents-toolkit. An agent skill from microsoft/work-iq.
1k GitHub starsUsed in 1 repo~2.3k tokens
Documents & OfficeAuto-check passed
Msgraph SDK
github/awesome-copilot
Official
Integrate Microsoft Graph SDK into any project — .NET, TypeScript/JavaScript, or Python.
40k GitHub stars~2.1k tokensUpdated today
Documents & OfficeAuto-check passed

Works with

Questions about Spfx Release

What does Spfx Release do?

Automate SPFx version releases - branch, update files, commit, open PR, then tag after merge. Spfx Release is an agent skill from pnp/docker-spfx.

When should I use Spfx Release?

Spfx Release fits situations like: tasks that involve Cloud office suites; tasks that involve Containers.

How do I install Spfx Release in Claude Code?

Run `npx skills add pnp/docker-spfx --skill spfx-release -a claude-code`. Or copy the skill folder (.claude/skills/spfx-release in pnp/docker-spfx) into .claude/skills/spfx-release in your project. Claude Code loads it when a task matches its description.

How do I install Spfx Release in Codex?

Run `npx skills add pnp/docker-spfx --skill spfx-release -a codex`. Or copy the skill folder (.claude/skills/spfx-release in pnp/docker-spfx) into .agents/skills/spfx-release in your project. Codex loads it when a task matches its description.

Can I use Spfx Release in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pnp/docker-spfx --skill spfx-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/spfx-release, .gemini/skills/spfx-release, .github/skills/spfx-release and .opencode/skills/spfx-release in your project.

What does Spfx Release need to run?

Going by SKILL.md and its folder, Spfx Release needs the command-line tools its instructions call (git and gh). Its frontmatter pre-approves these tools: Bash, Read, Edit, Grep.

Does Spfx Release access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Spfx Release safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Spfx Release use?

Spfx Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Spfx Release use?

About 572 tokens (SKILL.md is roughly 2.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Spfx Release?

Skills that share tags, products or a category with Spfx Release: Local Vscuse Validation (OfficeDev/microsoft-365-agents-toolkit, 781 stars), Sap Btp Build Work Zone Advanced (secondsky/sap-skills, 462 stars), CLI Microsoft365 (pnp/cli-microsoft365-mcp-server, 131 stars) and CLI Microsoft365 Script (pnp/cli-microsoft365-mcp-server, 131 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Spfx Release?

pnp (a GitHub organization) maintains it in pnp/docker-spfx, which has 134 GitHub stars. The repository was last updated on July 3, 2026.

Source: pnp/docker-spfx on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Spfx Release

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

SPFx Release Automation

Pre-flight checks

Steps to perform

Files

Compare with similar skills

Similar skills

Local Vscuse Validation

Sap Btp Build Work Zone Advanced

CLI Microsoft365

CLI Microsoft365 Script

Slack To Teams

Msgraph SDK

Related

Questions about Spfx Release