pr-to-production
PR to Production Branch (Release)
Create release PR from main to production for semantic-release.
Workflow
-
Fetch latest from remote (required first):
git fetch origin production main --quiet- IMPORTANT: Always use remote refs (
origin/production,origin/main) for comparison. Local branches may be stale.
-
Gather context (parallel):
git log origin/production..origin/main --onelinefor 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 -1for latest release version from remotegit rev-list --count origin/production..origin/mainto check if main is ahead of production
-
Analyze commits:
- Categorize by type: feat, fix, chore, etc.
- Calculate expected version bump
More from breaking-brake/cc-wf-studio
code-review-small
Quick code review for small PRs (<100 lines). Focuses on basic code quality, naming conventions, and obvious bugs.
37code-review-large
In-depth code review for large PRs (>500 lines). Full analysis including architecture, performance, security, and maintainability.
35code-review-medium
Standard code review for medium PRs (100-500 lines). Includes code quality, security basics, and test coverage analysis.
34code-review
Analyze PR diffs and generate review comments from code quality, security, and performance perspectives. Use for code reviews, quality checks, and security analysis.
33pr-to-main
Create a PR to main branch for feature/fix changes. Use when the user says "PRを作成", "mainにPR", or wants to submit changes for review.
1cc-workflow-ai-editor
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.
1