ship

Agent Skills › plugin87/ux-ui-agent-skills › ship

GitHub

发布前质量门禁，执行响应式、准确率及UI检查，生成包含版本号和变更日志的发布清单，等待确认后才允许打标签或发布。

.claude/skills/ship/SKILL.md plugin87/ux-ui-agent-skills

触发场景

准备标记新版本执行发布前最终检查生成发布说明

安装

npx skills add plugin87/ux-ui-agent-skills --skill ship -g -y

更多选项

非标准路径

npx skills add https://github.com/plugin87/ux-ui-agent-skills/tree/main/.claude/skills/ship -g -y

不安装直接使用

npx skills use plugin87/ux-ui-agent-skills@ship

指定 Agent (Claude Code)

npx skills add plugin87/ux-ui-agent-skills --skill ship -a claude-code -g -y

安装 repo 全部 skill

npx skills add plugin87/ux-ui-agent-skills --all -g -y

预览 repo 内 skill

npx skills add plugin87/ux-ui-agent-skills --list

SKILL.md

Frontmatter

{
    "name": "ship",
    "description": "Pre-release gate. Run the full gate, responsive + render checks, then produce the release checklist (README badge\/current\/changelog). Use before tagging a release.",
    "disable-model-invocation": true
}

Step 0: is the kit here? This skill reads files from the kit. Check once: ls ${CLAUDE_SKILL_DIR}/../../../tokens >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSING On KIT_MISSING only the skill folders were installed, which is what npx skills add does. Say so plainly, point the user at npx ux-ui-agent-skills init or the plugin install, and stop. Do not guess the contents of a file you could not open.

Gate first, then prepare the release. Do nothing destructive without explicit confirmation (no tag, no publish). This command verifies and drafts only.

Quality gate (must be fully green before continuing):
- node ${CLAUDE_SKILL_DIR}/../../../scripts/accuracy_report.mjs: report the real N/N.
- node ${CLAUDE_SKILL_DIR}/../../../scripts/verify_responsive.mjs examples: no overflow from 280 to 951px, hinge clear when folded.
- python3 ${CLAUDE_SKILL_DIR}/../../../scripts/check_no_emoji.py: UI + taste + instruction surface. If anything fails, stop and fix; do not proceed to the checklist.
Release checklist (per the project release rule):
- Update README.md: version badge, "current" line, and changelog entry.
- Confirm the bump level (major/minor/patch) with the user. It is their call.
- Confirm examples/apple-home stays gitignored (local IP).
- List the commits since the last tag so the changelog is accurate.
Output a ready-to-review summary: the green N/N line, the proposed version, and the drafted changelog entry. Wait for the user to approve before any git tag / publish step.