pr-to-production

This skill acts as a release engineering assistant designed for repositories utilizing semantic-release workflows. It streamlines the transition from development to production by automating the creation of release pull requests. The agent fetches remote state from both main and production branches to ensure accurate comparison, analyzes commit histories, and determines the appropriate version bump—major, minor, or patch—based on conventional commit types such as feat, fix, perf, and breaking changes. By using the gh CLI, it consistently formats release PRs, providing developers with clear summaries of included changes, calculated version increments, and automated release steps. This tool is intended for software engineers and release managers who want to reduce manual overhead in release preparation while maintaining strict adherence to versioning standards and commit history integrity. It handles the full lifecycle of PR creation, from remote synchronization to template generation, ensuring that all release notes, package.json updates, and build triggers are correctly prepared for final approval and merging. It is particularly effective for teams using GitHub Actions or similar CI/CD pipelines where merge commits are preferred to preserve history for automated tagging.

• Automatically categorizes commit messages (feat, fix, chore, docs) to determine version bumps.

• Fetches and synchronizes remote refs (origin/main and origin/production) to prevent stale state issues.

• Generates PR titles and bodies based on standardized templates (assets/pr-template.md).

• Calculates next semantic version (X.Y.Z) based on semantic-release logic.

• Preserves commit history by recommending merge commit strategies for production releases.

• Trigger this skill using natural language commands like 'リリースPR', 'productionにPR', or 'リリース準備'.

• Requires the GitHub CLI (gh) to be authenticated and configured in the environment.

• Always verifies the remote status before analysis to ensure the release PR is based on the absolute latest codebase.

• Ensure the repository contains a valid assets/pr-template.md for consistent release documentation.

• Note that this skill is specifically optimized for semantic-release versioning rules.