fishmark-release
Automates versioning and release workflows for the FishMark repository.
Install
mkdir -p .claude/skills/fishmark-release && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18688" && unzip -o skill.zip -d .claude/skills/fishmark-release && rm skill.zipInstalls to .claude/skills/fishmark-release
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
用于在 FishMark 仓库中执行正式 release 发版，适合需要升级版本号、整理 GitHub Release 正文、发布 Windows 安装包或预留 macOS 发版时使用。Key capabilities
- →Update version number in `package.json`
- →Organize and write GitHub Release body metadata
- →Execute Windows formal release
- →Reserve entry point for macOS release
- →Perform post-release verification
- →Summarize release status
How it works
The skill manages the formal release process for FishMark by updating version numbers, generating release notes, executing platform-specific build scripts, and performing post-release checks.
Inputs & outputs
When to use fishmark-release
- →Performing formal releases
- →Updating version metadata
- →Managing release notes generation
About this skill
FishMark 正式发版
Overview
这个 skill 负责 FishMark 的正式 release 流程，而不是单独跑一个脚本。
覆盖范围：
- 更新版本号
- 整理并写入 GitHub Release 正文元数据
- 执行 Windows 正式发版
- 为 macOS 保留统一流程入口
- 做发布后核对与总结
不负责：
- 顺手实现无关功能
- 擅自变更发布渠道、签名方案或核心技术栈
- 把未实现的平台说成已发布
Source Of Truth
- 版本号以
package.json为准 - GitHub Release 标题与正文以
release-metadata/release-notes.json为准 - Release 正文归纳优先读：
docs/plans/*handoff.mdreports/task-summaries/docs/progress.mddocs/decision-log.md
- Git 提交只作补充，不是唯一事实来源
Workflow
1. 预检
- 读取
package.json、docs/packaging.md、tools/release-win.bat、tools/release-macos.sh - 确认本次目标版本号和目标平台
- 检查工作区是否适合发版，避免把无关脏改动一并带入 release
2. 准备版本信息
- 更新
package.json的version - 同步更新
release-metadata/release-notes.json的version - 若两个版本不一致，停止发布
3. 整理 Release 正文
- 根据本次版本相关 task、handoff、summary 和决策记录归纳用户可感知变化
- 把标题和正文写入
release-metadata/release-notes.json - 不要把 GitHub Release 正文继续硬编码回脚本
参考：references/release-note-template.md
4. 执行发布
- Windows：运行
tools\\release-win.bat - macOS：运行
./tools/release-macos.sh前先确认脚本是否已实现；若仍是占位入口，明确停在“未实现”
5. 发布后核对
- Windows 至少核对：
release/latest.ymlrelease/FishMark-Setup-<version>.exerelease/FishMark-Setup-<version>.exe.blockmap- GitHub Release
v<version>的标题和正文是否与元数据一致
- macOS 当前只输出状态，不伪造成功结果
6. 总结
- 输出本次版本号
- 输出已发布平台与未发布平台
- 输出关键产物和剩余阻塞
参考：references/release-checklist.md
Platform Rules
- Windows：当前正式支持
- macOS：当前只保留入口与流程位置，未接入正式打包/发版实现
Stop Conditions
遇到以下情况必须停下：
package.json没有合法版本号release-metadata/release-notes.json缺失- release note 版本号与
package.json不一致 - Windows 发版脚本失败
- 用户要求发 macOS，但
tools/release-macos.sh仍是未实现占位
Completion
满足以下条件才算结束：
- 版本号已更新
- Release 标题与正文已写入元数据
- Windows 已发布成功，或已给出明确失败原因
- macOS 状态已明确说明
- 已完成发布后核对
- 已输出简短发版总结
When not to use it
- →When not performing a formal release for FishMark
- →When the goal is to implement unrelated features
- →When the user wants to change release channels or signing schemes
Limitations
- →Specific to the FishMark repository
- →macOS release is currently a placeholder without formal implementation
- →Does not support changing publishing channels, signing schemes, or core technology stack
How it compares
This skill automates and coordinates the entire FishMark release workflow, including metadata generation and platform-specific builds, unlike manual release steps.
Compared to similar skills
fishmark-release side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| fishmark-release (this skill) | 0 | 3mo | No flags | Advanced |
| gcp-cloud-run | 5 | 4mo | Review | Intermediate |
| flow-nexus-platform | 6 | 4mo | Review | Beginner |
| smithery-mcp-deployment | 8 | 8mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by yulu-gm
View all by yulu-gm →You might also like
gcp-cloud-run
aj-geddes
Deploy containerized applications on Google Cloud Run with automatic scaling, traffic management, and service mesh integration. Use for container-based serverless computing.
flow-nexus-platform
ruvnet
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges
smithery-mcp-deployment
CaullenOmdahl
Best practices for creating, optimizing, and deploying MCP servers to Smithery. Use this skill when:(1) Creating new MCP servers for Smithery deployment(2) Optimizing quality scores (achieving 90/100)(3) Troubleshooting deployment issues (0/0 tools, missing annotations, low scores)(4) Migrating existing MCP servers to Smithery format(5) Understanding Smithery's schema format requirements(6) Adding workflow prompts, tool annotations, or documentation resources(7) Configuring smithery.yaml and package.json for deployment
deployment-pipeline-design
wshobson
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.
vercel-deployment
davila7
Expert knowledge for deploying to Vercel with Next.js Use when: vercel, deploy, deployment, hosting, production.
netlify-deploy
openai
Deploy web projects to Netlify using the Netlify CLI (`npx netlify`). Use when the user asks to deploy, host, publish, or link a site/repo on Netlify, including preview and production deploys.