azure/typespec-go-bump-and-release
.github/skills/typespec-go-bump-and-release/SKILL.md
Upgrade tsp toolset dependencies for the @azure-tools/typespec-go package in Azure/autorest.go repo. Use when user wants to bump, update, or upgrade the TypeSpec toolset dependencies (e.g., @typespec/compiler, @typespec/http, @azure-tools/typespec-client-generator-core, @azure-tools/azure-http-specs), create a release PR, or publish a new version of typespec-go.
$ install --global
skillsauthnpx skillsauth add azure/autorest.go typespec-go-bump-and-releaseInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 3, 2026, 7:19 PM17.1s1 file scanned
SKILL.md
- name:
- typespec-go-bump-and-release
- description:
- Upgrade tsp toolset dependencies for the @azure-tools/typespec-go package in Azure/autorest.go repo. Use when user wants to bump, update, or upgrade the TypeSpec toolset dependencies (e.g., @typespec/compiler, @typespec/http, @azure-tools/typespec-client-generator-core, @azure-tools/azure-http-specs), create a release PR, or publish a new version of typespec-go.
TypeSpec Go Bump and Release
Upgrade the TypeSpec toolset dependencies for @azure-tools/typespec-go and create a release PR for the Azure/autorest.go repository.
Context Variables
- CURRENT_DATE: Current date in YYYY-MM-DD format (e.g., "2025-01-01")
Workflow
Step 1: Check and Upgrade TypeSpec Dependencies
- Change work directory to
packages/typespec-gofolder. - Run
ncu -uonpackage.jsonto check if there are any TypeSpec-related packages that need upgrading. Focus on packages matching:@typespec/*@azure-tools/typespec-*@azure-tools/azure-http-specs
- Review the proposed upgrades and apply them.
- Check and update the corresponding versions in
peerDependenciesofpackage.jsonto match the upgraded versions. For each upgraded package that also appears inpeerDependencies, update its version range accordingly.
Step 2: Install and Build
Run pnpm install from the repo root, and then run pnpm build from the packages/typespec-go directory:
cd <repo-root>
pnpm install
cd packages/typespec-go
pnpm build
This ensures pnpm-lock.yaml is updated and the project builds correctly.
Step 3: Run TypeSpec Compile
From the packages/typespec-go directory, run:
pnpm tspcompile
Notes:
- This command needs several minutes to finish; wait until it completes.
- If
pnpm tspcompilefails with any errors, stop immediately and report the error to the user. Do not proceed to subsequent steps until the error is resolved. - All changed files after
pnpm tspcompilemust be committed.
Step 4: Update CHANGELOG.md
Update packages/typespec-go/CHANGELOG.md with a new entry. The format should be:
## x.x.x ({{CURRENT_DATE}})
### Other Changes
* Updated to the latest tsp toolset.
Version rules:
- Run
git diffto inspect the changes. - The emitter is currently v0.x.x, semver rules are shifted: bump minor for breaking changes, patch for features/fixes/other.
- If there is already an unreleased version entry at the top, append the changelog entry into that existing version instead of creating a new one.
- Update the version in
packages/typespec-go/package.jsonto match.
Step 5: Stage, Commit and Push
git add -A && git commit -m "upgrade tsp toolset" && git push origin HEAD
Step 6: Create PR
If no existing PR exists for the current branch, create a new pull request targeting the main branch.
Related Skills
azure/typespec-go-add-spector-test
tools
VerifiedTrustedCommunity
Adds a Spector mock API test for the typespec-go emitter. Use when given a Spector case link (http-specs or azure-http-specs) to generate the Go client, add it to tspcompile.js, write `*_client_test.go` tests, and validate them against the Spector mock server.
78SKILL.mdUpdated Apr 3, 2026
openclaw/taskflow
tools
VerifiedTrustedCommunity
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
357,764SKILL.mdUpdated Apr 10, 2026
openclaw/extensions/lobster
tools
VerifiedTrustedCommunity
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
357,764SKILL.mdUpdated Apr 10, 2026
steipete/extensions/lobster
tools
VerifiedTrustedCommunity
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
357,588SKILL.mdUpdated Apr 13, 2026