gannonh/releasing-kata
.agents/skills/releasing-kata/SKILL.md
Use this skill when releasing Kata Desktop, Kata CLI, Kata Orchestrator, Kata Context, or Symphony, bumping versions, updating changelogs, or creating release PRs. Triggers include "release", "bump version", "publish", "create release PR", "ship it", "cut a release".
$ install --global
skillsauthnpx skillsauth add gannonh/kata-cloud-agents releasing-kataInstall 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 14, 2026, 3:00 AM25.4s7 files scanned
SKILL.md
- name:
- releasing-kata
- description:
- Use this skill when releasing Kata Desktop, Kata CLI, Kata Orchestrator, Kata Context, or Symphony, bumping versions, updating changelogs, or creating release PRs. Triggers include "release", "bump version", "publish", "create release PR", "ship it", "cut a release".
Releasing Kata
Kata has five independently versioned release targets. Ask which target if not clear from context.
| Target | Package | Tag Format | Reference |
| ---------------- | ------------------------ | ----------------- | -------------------------------- |
| Desktop | Desktop app (not npm package) | desktop-vX.Y.Z | references/desktop-release.md |
| CLI | @kata-sh/cli | cli-vX.Y.Z | references/cli-release.md |
| Orchestrator | @kata-sh/orc | orc-vX.Y.Z | references/orc-release.md |
| Context | @kata/context | context-vX.Y.Z | references/context-release.md |
| Symphony | symphony (Rust binary) | symphony-vX.Y.Z | references/symphony-release.md |
Root package.json version is 0.0.0 — never touch it. Each app owns its own version. Versions are independent and do not need to match.
Version semantics
| Type | When | Example |
| ------- | --------------------------------- | -------------- |
| patch | Bug fixes, small improvements | 0.4.9 → 0.4.10 |
| minor | New features, backward compatible | 0.4.9 → 0.5.0 |
| major | Breaking changes | 0.4.9 → 1.0.0 |
Workflow
Once the target is identified, read the corresponding reference file for the full release steps, CI behavior, and acceptance criteria. Then follow it.
Troubleshooting
For build failures, code signing, notarization, and CI issues, read release-troubleshooting.md.
Quick checks:
- CI didn't trigger: Version in
package.jsonmust differ from existing git tags - Desktop CI fails:
gh run list --workflow=desktop-release.yml --limit 3 - CLI publish fails: Ensure
NPM_TOKENsecret is set andprivate: falseinapps/cli/package.json - Orchestrator CI didn't trigger: Changes must be under
apps/orchestrator/**; version must differ from existingorc-v*tags - Orchestrator publish fails: Ensure
NPM_TOKENsecret is set; checkapps/orchestrator/package.jsonhas noprivate: true - Context CI didn't trigger: Changes must be under
apps/context/**; version must differ from existingcontext-v*tags - Context publish fails: Ensure
NPM_TOKENsecret is set; checkapps/context/package.jsonhas noprivate: true - Symphony CI didn't trigger: Changes must be under
apps/symphony/**; version inCargo.tomlmust differ from existingsymphony-v*tags - Symphony build fails: Ensure Rust toolchain is installed; check
cargo build --releaselocally first - macOS notarization fails: Verify
APPLE_ID,APPLE_APP_SPECIFIC_PASSWORD,APPLE_TEAM_IDsecrets
Related Skills
gannonh/spec-elicitation
tools
VerifiedTrustedCommunity
This skill should be used when a new project session starts and the user expresses what they want to build, asks to "start a project", "spec this out", "help me plan", or describes a feature/tool/system they want to create. Guides structured intent capture through goal, constraints, architecture, acceptance criteria, tasks, and non-goals.
27SKILL.mdUpdated Apr 5, 2026
gannonh/sym-push
tools
VerifiedTrustedCommunity
Push current branch changes to origin and create or update the corresponding pull request (with the correct base branch); use when asked to push, publish updates, or create pull request.
27SKILL.mdUpdated Apr 5, 2026
gannonh/sym-pull
development
VerifiedTrustedCommunity
Pull latest origin/<base-branch> into the current local branch and resolve merge conflicts (aka update-branch). Use when Codex needs to sync a feature branch with origin, perform a merge-based update (not rebase), and guide conflict resolution best practices.
27SKILL.mdUpdated Apr 5, 2026
gannonh/sym-linear
tools
VerifiedTrustedCommunity
Use Symphony's `linear_graphql` client tool for raw Linear GraphQL operations such as comment editing and upload flows.
27SKILL.mdUpdated Apr 5, 2026