@waoooo/claude-skills 1.0.0

package/skills/release-automation/SKILL.md

@@ -0,0 +1,306 @@
+---
+name: release-automation
+description: Automate version release workflow. Handles version updates, CHANGELOG generation, Git commits, tags, and GitHub Release creation. Use when user says "release", "发布", "发版", "publish new version". Supports semantic versioning for npm packages, frontend projects, and backend projects.
+---
+
+# Release Automation
+
+Automate the complete version release workflow with semantic versioning.
+
+## Current project info
+
+!`[ -f package.json ] && echo "Project: $(jq -r '.name // "unknown"' package.json), Version: $(jq -r '.version // "0.0.0"' package.json)" || echo "No package.json found"`
+
+## Core workflow
+
+### 1. Detect project type and current version
+
+```bash
+# Check if npm package
+if [ -f "package.json" ]; then
+  PROJECT_TYPE="npm"
+  CURRENT_VERSION=$(jq -r '.version' package.json)
+  PROJECT_NAME=$(jq -r '.name' package.json)
+else
+  # Try to get version from git tags
+  CURRENT_VERSION=$(git describe --tags --abbrev=0 2>/dev/null | sed 's/^v//')
+  PROJECT_TYPE="git-tags"
+fi
+
+echo "Current version: $CURRENT_VERSION"
+```
+
+### 2. Ask user for version type
+
+**ALWAYS ask user:**
+```
+Current version: 1.2.3
+
+What type of release?
+1. major (2.0.0) - Breaking changes
+2. minor (1.3.0) - New features
+3. patch (1.2.4) - Bug fixes
+4. custom - Specify version manually
+```
+
+### 3. Calculate new version
+
+```bash
+# Parse current version
+IFS='.' read -r MAJOR MINOR PATCH <<< "$CURRENT_VERSION"
+
+# Calculate based on type
+case "$VERSION_TYPE" in
+  major)
+    NEW_VERSION="$((MAJOR + 1)).0.0"
+    ;;
+  minor)
+    NEW_VERSION="${MAJOR}.$((MINOR + 1)).0"
+    ;;
+  patch)
+    NEW_VERSION="${MAJOR}.${MINOR}.$((PATCH + 1))"
+    ;;
+  custom)
+    # User provides NEW_VERSION
+    ;;
+esac
+
+echo "New version: $NEW_VERSION"
+```
+
+### 4. Validate new version
+
+```bash
+# Check if version already exists in CHANGELOG
+if [ -f "CHANGELOG.md" ]; then
+  if grep -q "## \[$NEW_VERSION\]" CHANGELOG.md; then
+    echo "ERROR: Version $NEW_VERSION already exists in CHANGELOG.md"
+    exit 1
+  fi
+fi
+
+# Check if git tag already exists
+if git rev-parse "v$NEW_VERSION" >/dev/null 2>&1; then
+  echo "ERROR: Git tag v$NEW_VERSION already exists"
+  exit 1
+fi
+```
+
+### 5. Generate release notes from git commits
+
+```bash
+# Get commits since last tag
+LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
+
+if [ -n "$LAST_TAG" ]; then
+  COMMITS=$(git log ${LAST_TAG}..HEAD --oneline)
+else
+  # If no tags, get recent commits
+  COMMITS=$(git log --oneline --since="1 month ago")
+fi
+
+# Categorize by conventional commit type
+echo "### Added"
+echo "$COMMITS" | grep "^[a-f0-9]* feat" | sed 's/^[a-f0-9]* feat[^:]*: /- /'
+
+echo "### Fixed"
+echo "$COMMITS" | grep "^[a-f0-9]* fix" | sed 's/^[a-f0-9]* fix[^:]*: /- /'
+
+echo "### Changed"
+echo "$COMMITS" | grep "^[a-f0-9]* refactor\|chore\|perf" | sed 's/^[a-f0-9]* [^:]*: /- /'
+```
+
+### 6. Update version files
+
+**For npm projects (package.json exists):**
+```bash
+# Update package.json
+jq ".version = \"$NEW_VERSION\"" package.json > package.json.tmp
+mv package.json.tmp package.json
+
+# Update package-lock.json if exists
+if [ -f "package-lock.json" ]; then
+  jq ".version = \"$NEW_VERSION\"" package-lock.json > package-lock.json.tmp
+  mv package-lock.json.tmp package-lock.json
+fi
+```
+
+**For other projects:**
+```bash
+# Create or update VERSION file
+echo "$NEW_VERSION" > VERSION
+```
+
+### 7. Update CHANGELOG.md
+
+```bash
+# Get current date
+DATE=$(date +%Y-%m-%d)
+
+# Prepare new entry
+NEW_ENTRY="## [$NEW_VERSION] - $DATE
+
+$RELEASE_NOTES
+"
+
+# Insert at top of CHANGELOG (after title)
+if [ -f "CHANGELOG.md" ]; then
+  # Insert after first line (title)
+  sed -i.bak "1a\\
+$NEW_ENTRY" CHANGELOG.md
+else
+  # Create new CHANGELOG
+  echo "# Changelog
+
+$NEW_ENTRY" > CHANGELOG.md
+fi
+```
+
+### 8. Commit changes
+
+```bash
+git add .
+git commit -m "chore: release v$NEW_VERSION"
+```
+
+### 9. Create Git tag
+
+```bash
+# Create annotated tag
+git tag -a "v$NEW_VERSION" -m "Release v$NEW_VERSION"
+```
+
+### 10. Push to remote
+
+```bash
+# Push commits
+git push origin $(git branch --show-current)
+
+# Push tag
+git push origin "v$NEW_VERSION"
+```
+
+### 11. Create GitHub Release
+
+```bash
+# Extract release notes for this version from CHANGELOG
+RELEASE_BODY=$(sed -n "/## \[$NEW_VERSION\]/,/## \[/p" CHANGELOG.md | sed '$d')
+
+# Create GitHub Release
+gh release create "v$NEW_VERSION" \
+  --title "Release v$NEW_VERSION" \
+  --notes "$RELEASE_BODY"
+```
+
+### 12. NPM publish (optional, for npm packages)
+
+**Ask user:** "Publish to npm?"
+
+If yes:
+```bash
+npm publish
+```
+
+**Note**: If 2FA is enabled, user must enter code manually.
+
+## Important rules
+
+- **ALWAYS** validate version doesn't already exist
+- **ALWAYS** generate release notes from git commits
+- **ALWAYS** ask user before publishing to npm
+- **NEVER** skip version validation
+- **NEVER** force push tags
+- **NEVER** publish without user confirmation
+
+## Error handling
+
+### Version already exists
+
+If version exists in CHANGELOG or git tags:
+```
+ERROR: Version 1.2.3 already exists
+- Found in CHANGELOG.md
+- Git tag v1.2.3 exists
+
+Please choose a different version.
+```
+
+### No git tags found
+
+If no previous tags exist:
+```
+No previous tags found. Using all commits from last month for release notes.
+```
+
+### GitHub CLI not authenticated
+
+If `gh` command fails:
+```bash
+# Check authentication
+gh auth status
+
+# If not authenticated
+gh auth login
+```
+
+### NPM publish fails
+
+If npm publish fails:
+```
+NPM publish failed. Common reasons:
+1. Not logged in: npm login
+2. No permission: Check package ownership
+3. Version already published: Bump version again
+```
+
+## Examples
+
+### Release patch version (bug fix)
+```bash
+# User: "发布新版本，修复了一些 bug"
+
+# Current: 1.2.3
+# Type: patch
+# New: 1.2.4
+
+# Auto-generate release notes from commits
+# Update package.json, CHANGELOG.md
+# Commit, tag, push
+# Create GitHub Release
+```
+
+### Release minor version (new feature)
+```bash
+# User: "release new version with new features"
+
+# Current: 1.2.3
+# Type: minor
+# New: 1.3.0
+
+# Auto-generate release notes
+# Update files, commit, tag, push
+# Create GitHub Release
+```
+
+### Release major version (breaking changes)
+```bash
+# User: "发布 2.0 版本"
+
+# Current: 1.9.5
+# Type: major
+# New: 2.0.0
+
+# Auto-generate release notes
+# Update files, commit, tag, push
+# Create GitHub Release
+```
+
+## Notes
+
+- Works in **current directory** (uses `pwd`)
+- No hardcoded paths
+- Auto-detects project type (npm or git-tags)
+- Generates release notes from git commits
+- Follows semantic versioning
+- Compatible with any git repository
+- Supports npm packages (optional publish)

package/skills/requirement-parse/SKILL.md

@@ -0,0 +1,212 @@
+# Skill: requirement-parse
+
+## 功能
+
+解析 OpenSpec 提案，推断能力配置，合并生成统一需求规范。
+
+## 何时调用
+
+- Job 创建完成后
+- OpenSpec 生成完成后
+- 需要生成 unified.json 时
+
+## 输入
+
+- `jobId` - Job ID（例如：2026-02-10-1520-pricing-system）
+- `openspecPath` - OpenSpec 目录路径（例如：openspec/changes/001-pricing-system/）
+
+## 输出
+
+- `parsed/docs.json` - 从 OpenSpec 解析的需求
+- `parsed/form.json` - 推断的能力配置
+- `parsed/unified.json` - 合并后的统一规范
+
+## 执行步骤
+
+### 1. 解析 OpenSpec
+
+```bash
+pnpm spec:parse-openspec \
+  <openspec-path> \
+  exports/jobs/<job-id>/parsed/docs.json
+```
+
+**输出**：`docs.json`
+```json
+{
+  "version": "1.0.0",
+  "sources": {
+    "docs": {
+      "files": ["planning/pricing-system.mdx"],
+      "extractedAt": "2026-02-10T15:20:00Z"
+    }
+  },
+  "requirements": [
+    {
+      "reqId": "REQ-PRICING-021",
+      "title": "多货币支持",
+      "description": "支持 USD, CNY, JPY, EUR...",
+      "source": "docs",
+      "type": "feature",
+      "status": "draft",
+      "acceptance": ["支持 4+ 货币"],
+      "tasks": ["实现货币转换"]
+    }
+  ]
+}
+```
+
+### 2. 推断能力配置
+
+```bash
+pnpm spec:infer-builder \
+  exports/jobs/<job-id>/parsed/docs.json \
+  exports/jobs/<job-id>/parsed/form.json
+```
+
+**输出**：`form.json`
+```json
+{
+  "version": "1.0.0",
+  "sources": {
+    "builder": {
+      "method": "inferred",
+      "extractedAt": "2026-02-10T15:20:05Z"
+    }
+  },
+  "requirements": [
+    {
+      "reqId": "REQ-BUILDER-AUTH",
+      "title": "集成 auth 能力",
+      "source": "builder",
+      "type": "feature",
+      "status": "ready",
+      "layerHint": "L1",
+      "capabilityHints": ["auth"]
+    }
+  ]
+}
+```
+
+### 3. 合并需求
+
+```bash
+pnpm spec:merge \
+  exports/jobs/<job-id>/parsed/docs.json \
+  exports/jobs/<job-id>/parsed/form.json \
+  exports/jobs/<job-id>/parsed/unified.json
+```
+
+**输出**：`unified.json`
+```json
+{
+  "version": "1.0.0",
+  "sources": {
+    "docs": {...},
+    "builder": {...}
+  },
+  "requirements": [
+    {
+      "reqId": "REQ-PRICING-021",
+      "title": "多货币支持",
+      "description": "...",
+      "source": "merged",
+      "layerHint": "L2",
+      "capabilityHints": ["payment-gateway", "pricing"],
+      "acceptance": [...],
+      "tasks": [...],
+      "blockedBy": [],
+      "blocks": []
+    }
+  ],
+  "executionOrder": ["REQ-PRICING-021", "REQ-PRICING-022"]
+}
+```
+
+### 4. 验证输出
+
+- 检查三个文件是否都生成
+- 检查 JSON 格式是否正确
+- 检查需求数量是否合理
+
+## 使用示例
+
+### 示例 1：完整流程
+
+```
+Agent 调用 requirement-parse:
+  输入:
+  - jobId: 2026-02-10-1520-pricing-system
+  - openspecPath: openspec/changes/001-pricing-system/
+
+执行:
+  🔧 步骤 1: 解析 OpenSpec
+  ⏳ 运行: pnpm spec:parse-openspec
+  ✅ 生成: docs.json (5 个需求)
+
+  🔧 步骤 2: 推断配置
+  ⏳ 运行: pnpm spec:infer-builder
+  ✅ 生成: form.json (推断出 3 个能力)
+
+  🔧 步骤 3: 合并需求
+  ⏳ 运行: pnpm spec:merge
+  ✅ 生成: unified.json (5 个需求 + 能力标注)
+
+显示结果:
+  ✅ 需求解析完成
+  📊 统计:
+  - 总需求: 5 个
+  - 推断能力: 3 个 (auth, payment, pricing)
+  - 执行顺序: 5 个任务
+```
+
+## 错误处理
+
+### 错误 1：OpenSpec 解析失败
+
+```
+❌ 错误: OpenSpec 解析失败
+🔍 原因: 找不到 proposal.md 或格式不正确
+
+💡 建议:
+1. 检查 OpenSpec 目录是否存在
+2. 确认包含 proposal.md, design.md, tasks.md
+3. 检查文件格式是否正确
+```
+
+### 错误 2：推断失败
+
+```
+❌ 错误: 无法推断能力配置
+🔍 原因: 需求描述中没有能力关键词
+
+💡 建议:
+1. 手动创建 form.json
+2. 使用 Builder UI 填写表单
+3. 在 MDX 中添加更多能力关键词
+```
+
+### 错误 3：合并冲突
+
+```
+❌ 错误: 需求 ID 冲突
+🔍 原因: docs.json 和 form.json 有相同的 reqId
+
+💡 建议:
+1. 检查两个文件的需求 ID
+2. 手动调整冲突的 ID
+3. 重新运行合并
+```
+
+## 相关脚本
+
+- `src/scripts/parse-openspec.ts` - 解析 OpenSpec
+- `src/scripts/infer-builder-config.ts` - 推断配置
+- `src/scripts/merge-requirements.ts` - 合并需求
+
+## 注意事项
+
+1. **顺序执行** - 三个步骤必须按顺序执行
+2. **依赖关系** - 每步依赖前一步的输出
+3. **错误停止** - 任何步骤失败立即停止
+4. **保留中间文件** - 方便调试和回溯