hatch3r-pr-creation

To create a pull request that follows repository conventions, the Skill enforces branch naming patterns, fills all template sections, runs a quality and security checklist, and delegates code review before opening the PR.

To prepare a merge request for CI readiness, the workflow detects the GitLab platform, targets the configured default branch, runs a self-review checklist, and requires a rollout and rollback plan before creating the MR.

Yes, the PR creation workflow is platform-aware, detecting whether to use a pull request for GitHub or Azure DevOps, and a merge request for GitLab, using the correct CLI per platform configuration to create the request.

The best way to ensure branch naming compliance is using an automated format policy that validates branch names, checks for default-branch targeting, and handles common creation failures like missing remote branches before submitting the PR.

Pull request creation can fail due to missing remote branches, incorrect draft versus ready state, or default-branch targeting violations, which the Skill validates against before using the platform CLI to create the request.

Yes, you can generate a rollout and rollback plan inside the pull request template, as the Skill fills all template sections and requires reliable rollout guardrails before spawning the required reviewer agent.