deploy-agent-sessions
Skill941 starsChanged 11 days agoMITView on GitHub
Release/deploy workflow for Agent Sessions (Sparkle appcast + GitHub release). Use when asked to "deploy", "ship", "publish", or "prepare a production release" for this repo. Follows the repo’s canonical deploy skill at `.claude/skills/deploy.md` and the runbook at `docs/deployment.md`.
- Commits and pushes
In this repository9 other files it gives its agents.
- agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-session-format-checkSkill
- deploySkill
- release-notesSkill
- add-agent-supportSkill
- agent-session-format-checkSkill
- agent-support-matrixSkill
- sc-skillSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
When working in the Agent Sessions repo, treat these as the single source of truth:
- Distinctive: line 16
If this skill conflicts with any of the above, follow the repo docs.
- Distinctive: line 20
Always deploy from the user’s current local repository checkout.
- Distinctive: line 21
Do not create temporary clones or alternate worktrees to work around a dirty tree.
- Distinctive: line 22
If the local worktree is dirty, stop and advise the user to clean it first (commit, stash, or discard), then continue in the same local …
- Very specific: line 26
Use the unified deploy tool, following .claude/skills/deploy.md:
- Very specific: line 41
Ensure user-visible notes are updated (per .claude/skills/deploy.md): docs/CHANGELOG.md, monthly summary in docs/summaries/YYYY-MM.md, and …
- Very specific: line 42
Run tools/release/deploy qa --version <VERSION> on the exact release commit.
- Very specific: line 44
If user-facing SwiftUI copy changed, update AgentSessions/Resources/Localizable.xcstrings in the same change.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Agent Sessions Deploy
Canonical sources
When working in the Agent Sessions repo, treat these as the single source of truth:
.claude/skills/deploy.mddocs/deployment.md- Unified tool:
tools/release/deploy(start withtools/release/deploy --help)
If this skill conflicts with any of the above, follow the repo docs.
Workspace policy (mandatory)
- Always deploy from the user’s current local repository checkout.
- Do not create temporary clones or alternate worktrees to work around a dirty tree.
- If the local worktree is dirty, stop and advise the user to clean it first (commit, stash, or discard), then continue in the same local repo.
Default workflow (command sequence)
Use the unified deploy tool, following .claude/skills/deploy.md:
tools/release/deploy changelog [FROM_TAG]
tools/release/deploy qa --version <VERSION>
tools/release/deploy bump [patch|minor|major]
git push origin main
tools/release/deploy qa --version <VERSION>
tools/release/deploy release <VERSION> [--dry-run]
tools/release/deploy verify <VERSION>Before running release
- Confirm target version string (
X.Yfor major/minor releases,X.Y.Zonly for patch releases) and whether this is a patch/minor/major bump. Never shipX.Y.0. - Ensure user-visible notes are updated (per
.claude/skills/deploy.md):docs/CHANGELOG.md, monthly summary indocs/summaries/YYYY-MM.md, and any required public copy updates. - Run
tools/release/deploy qa --version <VERSION>on the exact release commit. QA requires a cleanmaincheckout synced withorigin/main;tools/release/deploy releaseandtools/release/deploy resumerequire its fresh QA stamp unless--skip-qa/SKIP_QA=1is explicit. - The QA gate is CI-parity: it verifies the pinned Xcode toolchain, runs the docs guards and localization catalog validation, runs a no-signing Debug build in
.deriveddata-localization, and runs localization extraction-drift validation before writing the QA stamp. A green XCTest run alone is not release-ready. - If user-facing SwiftUI copy changed, update
AgentSessions/Resources/Localizable.xcstringsin the same change. Keep intentional raw paths, commands, and identifiers asText(verbatim:); add validator verbatim exceptions only after review. tools/release/deploy bumprequires the target-version QA stamp before changing release metadata; after pushing the bump commit, rerun exact-commit QA before release. Never use the manual fallback to bypass a failed QA/extraction gate.- Local QA must match
tools/release/ci-xcode-version.txt; CI selects that toolchain on the pinnedmacos-26image. - Expect Release builds to spend several minutes in
swift-frontendduring whole-module optimization; the build helper now prints heartbeats. If interrupted after the notarized DMG is built, prefertools/release/deploy resume, which validates the saved gitHEADbefore continuing.
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.

