// Create a release PR from main to production branch. Use when the user says "リリースPR", "productionにPR", "リリース準備", or wants to trigger a release.
Use the `ccwf` CLI (from @cc-wf-studio/cli) to render, validate, preview, export, or run cc-wf-studio workflow JSON files from the terminal. Apply whenever the user mentions viewing, visualizing, checking, executing, or converting a workflow under `.vscode/workflows/` (or any `*workflow*.json`), wants a Mermaid diagram of a workflow, asks to "see" / "preview" / "open" a workflow, or wants to run a workflow as a Claude Code Skill without opening VSCode.
Use when modifying `resources/workflow-schema.json` in cc-wf-studio to influence how AI agents generate workflows via the cc-workflow-ai-editor skill. Triggers include "AIが特定のノードタイプを選んでくれない", "ワークフロー生成のバイアスを調整したい", "スキーマの description を変えたい", "新しいノードタイプを追加したい", "嘘の制約がスキーマに混じっていないか確認したい". Covers what the schema actually does (instructions to AI, not runtime constraints), the design philosophy (align direction, do not prescribe rules), the build pipeline (.json → .toon auto-generated), and known bias sources to audit.
AI workflow editor for CC Workflow Studio. Create and edit visual AI agent workflows through interactive conversation using MCP tools (get_workflow_schema, get_current_workflow, apply_workflow, update_nodes). Use when the user wants to create a new workflow, modify an existing workflow, or edit the workflow canvas in CC Workflow Studio via the built-in MCP server.
Analyze PR review comments from a GitHub PR URL. Fetch review comments, verify each finding against the actual codebase, assess validity (correct/incorrect/partial), present a structured summary with recommended actions, and optionally reply to each comment on GitHub. Use when given a PR review URL or when asked to check/analyze PR feedback.
Jiraチケットの要件とConfluenceの関連ドキュメントを基に、Frontend/Backend/Infrastructureに分割した実装計画を策定するプランニングスキル。Jiraチケット情報とConfluence検索結果が前段で取得済みであることを前提とし、構造化された実装計画を出力する。「プランニング」「実装計画策定」「タスク分割」などの文脈で使用。
Clean up merged feature branches after PR to main is merged. Use when the user says "ブランチ削除", "cleanup", "マージ後の片付け", or wants to delete a merged branch.
| name | pr-to-production |
| description | Create a release PR from main to production branch. Use when the user says "リリースPR", "productionにPR", "リリース準備", or wants to trigger a release. |
Create release PR from main to production for semantic-release.
Fetch latest from remote (required first):
git fetch origin production main --quietorigin/production, origin/main) for comparison. Local branches may be stale.Gather context (parallel):
git log origin/production..origin/main --oneline for commits to releasegit ls-remote --tags origin | grep -E 'refs/tags/v[0-9]+\.[0-9]+\.[0-9]+$' | sed 's/.*refs\/tags\///' | sort -V | tail -1 for latest release version from remotegit rev-list --count origin/production..origin/main to check if main is ahead of productionAnalyze commits:
Create PR:
gh pr create with base productionassets/pr-template.mdfeat: → minor (1.0.0 → 1.1.0)fix:, perf:, revert: → patch (1.0.0 → 1.0.1)BREAKING CHANGE → major (1.0.0 → 2.0.0)docs:, chore:, ci: → no bumpLanguage: Always write PR title and body in English
Title: Release: vX.Y.Z
Body: Use template at assets/pr-template.md
gh pr create --base production --title "Release: v0.2.0" --body "$(cat <<'EOF'
## Summary
Merge latest changes from `main` to `production` for automated release v0.2.0.
## Included Changes
### Features
- feat: add chunk-based translation for large documents (#5)
### Enhancements
- chore: setup semantic-release (#4)
## Release Version Calculation
**v0.2.0** (minor bump)
Semantic Release will analyze commits since v0.1.1:
- ✅ `feat: add chunk-based translation` (#5) → **minor bump**
- ❌ `chore: setup semantic-release` (#4) → no version bump
Result: **0.1.1 + minor = 0.2.0**
## CHANGELOG.md Contents
The following features will be included:
- Add chunk-based translation for large documents (#5)
Setup semantic-release (#4) will not appear in CHANGELOG.
## Release Automation
This merge will trigger:
1. Analyze commit messages (0.1.1 → 0.2.0)
2. Update version in package.json files
3. Generate CHANGELOG.md with features
4. Create GitHub release
5. Build and upload VSIX package
6. Sync version changes back to main
## Merge Strategy
**Use merge commit** (not squash) to preserve commit history for Semantic Release.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"