release
Skill3 starsChanged 4 days agoMITView on GitHub
Cut a release of the msteams channel plugin — validate, bump the version in all four manifests, write a CHANGELOG entry, commit, push, tag, and publish a GitHub release. Use whenever the user says "release", "cut a release", "version bump", "ship it", "publish", "tag a release", "changelog and push", or finishes a batch of changes and wants to ship them.
- Reads credentials
- Commits and pushes
193 other projects use a version of this.
Adopted by
Most recently taken up by
- yicheng47/runnertheir own version, first seen Nov 13, 2026
- eugene1g/agent-safehousetheir own version, first seen Nov 12, 2026
- BlockRunAI/ClawRoutertheir own version, first seen Nov 11, 2026
- cubeplexai/cubeplextheir own version, first seen Nov 10, 2026
- bex-co/bextheir own version, first seen Nov 10, 2026
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 9, 2026
Used with
Projects with it also use create-agent-adapter, changelog-style and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillcreate-agent-adapter
Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.
Also in 5 projects that use this
GrinvSkillchangelog-style
Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.
Also in 4 projects that use this
GrinvSkilldocs-consistency-check
Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.
Also in 4 projects that use this
Microsoft AzureSkillcomponent-release
Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.
Also in 4 projects that use this
Microsoft AzureSkilldocumentation-consistency
Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.
Also in 8 projects that use this
rivet-devSkilllaunch-graphics
Generate agentOS marketing/launch graphics (launch & social heroes, code-snippet cards) from the committed generators in docs-internal/graphics. Use when asked to make, update, or render an agentOS launch image, social image, "agentOS Apps" graphic, or technical code-snippet image.
Also in 3 projects that use this
- +3 more from Grinv
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 193
- paperclipai/paperclip★ 114ksame name
- modelcontextprotocol/servers★ 92ksame name
- remotion-dev/remotion★ 73ksame name
- traefik/traefik★ 66ksame name
- usememos/memos★ 64ksame name
- tw93/Pake★ 64ksame name
- amruthpillai/reactive-resume★ 46ksame name
- reactive-resume/reactive-resume★ 46ksame name
- AmruthPillai/Reactive-Resume★ 45ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
183 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. 0 are common, 8 are distinctive, and 9 are very specific to this project.
0
Common
Most of the 183 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 27
Every release sets all four to the same X.Y.Z.
- Distinctive: line 46
Run all of these first. Abort on any failure — a bad tag on a repo that *is* the distribution channel is live for users the moment it lands …
- Very specific: line 84
Wire-affecting change → the E2E smoke is mandatory: If this release touches the inbound pipeline (queue/gate/normalize), any outbound tool, …
- Very specific: line 113
Already-tagged fast-path: if HEAD already carries an msteams--v* tag, there is nothing to release.
- Very specific: line 116
Already-bumped fast-path: if plugin.json is ahead of the newest tag, the bump and CHANGELOG were done in an earlier session — skip to Step …
- Distinctive: line 141
wait for confirmation: before editing anything.
- Very specific: line 145
If CHANGELOG.md does not exist, create it:
- Very specific: line 157
Docs-only double-check first: Every bullet must describe a change an *operator or user* experiences.
- Very specific: line 219
All four must show $NEW. Then sweep for stray references to the *previous* version:
- Very specific: line 258
Add a body summarizing the release and any docs corrections kept out of the CHANGELOG.
- Distinctive: line 277
Never flip visibility without an explicit yes — publishing is irreversible in practice.
- Distinctive: line 333
Don't git add -A — stage release files by name.
- Distinctive: line 334
Don't tag off a non-main branch without the user's explicit go-ahead.
- Distinctive: line 335
Don't skip the production-install check in Step 1 — CI never exercises the path every user takes.
- Very specific: line 337
Don't ship a wire-affecting release on bun test alone.
- Distinctive: line 339
Don't bump the version anywhere before the user has confirmed the level in Step 3.
- Distinctive: line 340
Don't flip the repo to public as a side effect of releasing.
“Common” is measured: kept by at least 6 in 10 of the 183 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Release
Cut a release of the msteams channel plugin. This repo is its own marketplace:
the plugin lives at the repo root and .claude-plugin/marketplace.json points at
./, so users install it straight from GitHub with
/plugin marketplace add gtapps/msteams-channel. There is no registry and no
build artifact — the git tag plus the pushed commit are the release, and a
user's /plugin update pulls whatever main says.
That has one consequence worth internalizing before you start: an unreleased
commit on main is already live for anyone who runs /plugin marketplace update.
The tag is a marker for humans and for version-gated updates, not a gate on
distribution. So main must never carry a state you would not ship.
Usage
/release — infer the bump level from the changes since the last tag.
/release patch|minor|major — force a bump level.
/release 0.2.0 — force an exact version.
The four version locations
Every release sets all four to the same X.Y.Z. claude plugin tag only
checks the first and the third, so the other two are on you.
| Location | How to read it |
.claude-plugin/plugin.json | jq -r '.version' |
package.json | jq -r '.version' |
.claude-plugin/marketplace.json | jq -r '.plugins[] | select(.name=="msteams") | .version' |
server.ts | the { name: 'msteams', version: 'X.Y.Z' } literal in the Server constructor (~line 100) |
The server.ts literal is what a client sees in the MCP initialize response,
so a stale one misreports the running build to anyone debugging a live session.
Edit it with the Edit tool, never a blind sed — the file contains other
version strings.
Steps
1. Pre-release validation
Run all of these first. Abort on any failure — a bad tag on a repo that is the
distribution channel is live for users the moment it lands on main.
bun install --frozen-lockfile # lockfile must be current, not "fixable"
bun run typecheck # tsc --noEmit
bun test # 249+ tests, ~11s, no tenant or network
claude plugin validate . # must print Validation passed (warnings ok)Notes:
- A green run legitimately prints
access.json is corrupt, moved asideand the static-mode downgrade warning. Those are assertions, not failures. bun install --frozen-lockfilefailing meansbun.lockis behindpackage.json. Fix it withbun installand commit the lockfile before releasing — users install from this lockfile.claude plugin validate .is clean today.claude plugin tagadditionally warns thatCLAUDE.md/CLAUDE.local.mdat the plugin root aren't loaded as plugin context — expected, since the plugin root is the repo root. Warnings do not block a release; a hard✘does.
Then the check the suites cannot do — the production install path. Users never get devDependencies, so a devDep that leaked into runtime code passes CI and fails at their first launch:
D=$(mktemp -d) && cp package.json bun.lock "$D"/ \
&& (cd "$D" && bun install --production --frozen-lockfile --no-summary) \
&& grep -rn "jose\|jwks-rsa\|@types/bun\|typescript" server.ts src/*.ts send.ts \
&& echo "LEAK: a devDependency is imported by runtime code — stop" || echo "runtime deps clean"2. Drift the tests cannot see
Walk these four before deciding the bump. Each maps to something a user or operator holds that the test suite has no view of:
- Wire-affecting change → the E2E smoke is mandatory. If this release
touches the inbound pipeline (
queue/gate/normalize), any outbound tool,send.ts, the SDK pin, or the MCPinstructionsstring, the release is not valid onbun testalone. Follow the private procedure in.claude-code-hermit/compiled/topic-msteams-e2e-runs.mdagainst a live tenant, then append the result — build, date and any failed leg — to that gitignored topic. Both the procedure and run records are private operator knowledge. If the operator cannot run it now, say so plainly and let them decide whether to ship untested — do not quietly skip it. access.jsonschema change → operators hold a live copy in~/.claude/channels/msteams/. Any new, renamed, or newly-required key needs an explicit Upgrade Instructions step, andACCESS.md§ Config file must already describe it..envkey change (MSTEAMS_APP_ID/_APP_PASSWORD/_TENANT_ID, or a newMSTEAMS_*listener variable) → Upgrade Instructions step, plus the variable table inREADME.mdand the relevant step inSETUP.md.- SDK pin bump (
@microsoft/teams.apps/@microsoft/teams.api) → at minimum a minor, and it forces item 1. The pin is the one load-bearing upstream;tests/auth-coverage.test.tsfails loudly when a release moves the validators, which is the point, but a green suite does not prove the live wire still works.
Also confirm the prose still describes reality: README.md (tool table,
enablement, variable table), ACCESS.md, SETUP.md, CLAUDE.md
invariants. Fix inaccuracies in this release; docs-only corrections go in the
commit message, not the CHANGELOG.
3. Determine the version
Already-tagged fast-path: if HEAD already carries an msteams--v* tag,
there is nothing to release. Report it and stop.
Already-bumped fast-path: if plugin.json is ahead of the newest tag, the
bump and CHANGELOG were done in an earlier session — skip to Step 7's commit
check, then tag.
Normal path:
LAST=$(git tag --list 'msteams--v*' | sort -V | tail -1)
git log --oneline "$LAST"..HEAD
git diff --stat "$LAST"..HEADPre-1.0, so err toward minor whenever an operator could notice:
- Patch (0.0.X) — bug fixes, internal refactors, added tests, doc-only releases.
- Minor (0.X.0) — new tool, new meta key, gate/threading behavior change, new
or renamed
access.jsonor.envkey, SDK pin bump, anything requiring the operator to re-read a doc or touch their state dir. - Major (X.0.0) — only if the user explicitly asks, or for the 1.0.0 cut.
A security-relevant change to the gate, the outbound gate, the permission
relay, or credential handling is at least a minor however small the diff, and
its CHANGELOG bullet leads with security:.
Present the suggested version with a rationale naming the specific changes, and wait for confirmation before editing anything.
4. Write the CHANGELOG entry
If CHANGELOG.md does not exist, create it:
# Changelog
All notable changes to the msteams channel plugin are documented here.
This project adheres to [Semantic Versioning](https://semver.org/).Prepend the new entry directly after that header, before the previous version.
Rename an existing [Unreleased] section instead of prepending to it.
Docs-only double-check first. Every bullet must describe a change an
operator or user experiences. Verify against
git diff "$LAST"..HEAD -- server.ts src/ send.ts skills/ .claude-plugin/;
drop any bullet whose only backing change is a .md file or a comment.
Format:
## [X.Y.Z] - YYYY-MM-DD
### Added / Changed / Fixed / Security
(use whichever sections apply — skip empty ones)
- **subsystem: one-line summary** — optional ≤1-sentence rationale.
### Upgrade Instructions
1. **Imperative step title** — what to do, in one sentence.
No state-dir or credential changes required.Constraints:
- Narrative bullets —
- **subsystem: what changed** — short rationale if non-obvious.One line, ~40 words max. Lead with the subsystem in this codebase's own vocabulary:gate:,queue:,normalize:,outbound:,attachments:,access:,permissions:,send:,webhook:,security:,docs:. Do not list internal refactors, helper extractions, or test scaffolding — those live ingit diff. Upgrade Instructions — imperative, one action per numbered step, every step starting with a verb (
Run,Add,Replace,Re-pair,Restart). Include a step for each of:- New/renamed
access.jsonkey → name the key and its default. - New/renamed
MSTEAMS_*variable → name it and where it goes (.env, mode 0600). - Changed tool name or argument → the exact old→new call shape.
- Anything that changes the bot's Azure-side config (messaging endpoint, a new Graph permission) → the exact portal/CLI step, since that is not in the repo.
- A change to the MCP
instructionsstring or the channel registration →Restart the session with \claude --channels plugin:msteams@msteams-channel`.`
Close with
No state-dir or credential changes required.when true — it is the common case and operators scan for it.- New/renamed
- What belongs where: why it changed → the bullet. What the operator must
execute → Upgrade Instructions. A behavior delta needing no action → one final
line prefixed
**Note:**, not a numbered step. - Never put a credential, tenant id, AAD object id, conversation id, or attachment URL in the CHANGELOG. Same rule as the code: those are the things this plugin exists to keep out of logs.
5. Bump all four version locations
Edit each of the four from the table above, then confirm they agree:
NEW=X.Y.Z
jq -r '.version' .claude-plugin/plugin.json
jq -r '.version' package.json
jq -r '.plugins[] | select(.name=="msteams") | .version' .claude-plugin/marketplace.json
grep -n "name: 'msteams', version:" server.tsAll four must show $NEW. Then sweep for stray references to the previous
version:
grep -rn "$OLD" --include='*.md' --include='*.json' --include='*.ts' --include='*.yml' . \
| grep -v -E '(node_modules|\.claude-code-hermit|bun\.lock|CHANGELOG\.md)'CHANGELOG.md keeping old versions in its history is not drift.
6. Final validation
Steps 4–5 touch Markdown, JSON and one TS literal, so the suites need no re-run. Confirm the manifests still parse and the tree contains only release files:
jq -e . .claude-plugin/plugin.json > /dev/null
jq -e . .claude-plugin/marketplace.json > /dev/null
jq -e . package.json > /dev/null
claude plugin validate .
git status --shortgit status must show only CHANGELOG.md, the four version locations, and any
doc this release legitimately corrected. .claude-code-hermit/,
CLAUDE.local.md, .claude/settings.local.json, node_modules/ and
graphify-out/ are gitignored and must never appear. Anything unexpected →
investigate before committing.
7. Commit and push
Stage the release files by name — never git add -A; an accidentally staged
.env or state file in a public repo is unrecoverable. Commit with the house
format:
msteams v<X.Y.Z>: one-line summary of the releaseAdd a body summarizing the release and any docs corrections kept out of the
CHANGELOG. Push to origin.
8. Before tagging: branch and visibility
git branch --show-current
gh repo view gtapps/msteams-channel --json visibility -q .visibility- Not on
main→ stop, do not tag. Tagging a branch tip pins a SHA thatmainnever carries after a squash or rebase merge, stranding the tag on an orphan commit. Recommended path: open a PR, merge, re-run/releasefrommain(Step 3's fast-path jumps straight here). Offer tagging-now only as an explicit second option and wait for the user's choice. PRIVATE→ the release is not installable by anyone:/plugin marketplace add gtapps/msteams-channelfails against a private repo for everyone but the owner. Say so and ask whether to make it public (gh repo edit gtapps/msteams-channel --visibility public) before tagging. Never flip visibility without an explicit yes — publishing is irreversible in practice.
9. Tag and publish
The tag is msteams--v<X.Y.Z> (double dash) — what claude plugin tag produces.
It validates that plugin.json and the marketplace entry agree, requires a clean
tree, and refuses to clobber an existing tag:
claude plugin tag . --pushFall back to plain git only if that command is unavailable:
VERSION=$(jq -r '.version' .claude-plugin/plugin.json)
git tag -a "msteams--v$VERSION" -m "msteams v$VERSION"
git push origin "msteams--v$VERSION"Then create the GitHub release from the CHANGELOG section just written — not
--generate-notes, which would re-list raw commits over the curated entry:
VERSION=$(jq -r '.version' .claude-plugin/plugin.json)
TAG="msteams--v$VERSION"
NOTES_FILE=$(mktemp)
awk -v ver="$VERSION" '
$0 ~ "^## \\[" ver "\\]" {flag=1; next}
/^## \[/ && flag {exit}
flag {print}
' CHANGELOG.md > "$NOTES_FILE"
[ ! -s "$NOTES_FILE" ] && { echo "CHANGELOG section for $VERSION not found — fix and retry"; rm "$NOTES_FILE"; exit 1; }
gh release create "$TAG" --title "$TAG" --notes-file "$NOTES_FILE"
rm "$NOTES_FILE"Confirm the CI run on the pushed commit went green before announcing.
10. Report
Print the new version, the commit hash, the tag, the GitHub release URL, and whether the E2E smoke was run for this build (and if not, that it wasn't). Remind the user that existing installs pick this up with:
/plugin marketplace update msteams-channel
/plugin update msteams@msteams-channeland that the session must be relaunched with
claude --channels plugin:msteams@msteams-channel for a new build to take effect.
Don't
- Don't
git add -A— stage release files by name. - Don't tag off a non-
mainbranch without the user's explicit go-ahead. - Don't skip the production-install check in Step 1 — CI never exercises the path every user takes.
- Don't ship a wire-affecting release on
bun testalone; either run the private E2E procedure or state clearly that it wasn't run. - Don't bump the version anywhere before the user has confirmed the level in Step 3.
- Don't flip the repo to public as a side effect of releasing.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

