create-pr

Automating pull request creation involves enforcing conventional commits and running quality gate validation to generate clean, convention-compliant PRs. This skill detects project linting, formatting, and testing scripts before opening a PR, ensuring scope isolation and CI/CD integration without manual CLI overhead.

Yes, the GitHub CLI (gh) is required to automate pull request generation and commit linting. The CLI manages remote repository interactions and quality gate execution, allowing the workflow to automatically verify Git scopes, run project-specific build tools, and open convention-compliant pull requests.

The best way to enforce quality gates before opening a Git pull request is to automatically detect and run linting, formatting, and testing scripts defined in your project. This approach verifies code cleanliness, ensures commit messages follow project conventions, and handles runbook references and breaking changes.

Yes, you can standardize PR formatting and commit messages for CI/CD integration workflows by automating scope isolation and quality gate validation. This ensures commit messages and PR bodies follow project-specific conventions, including proper handling of runbook references and breaking changes, producing perfectly formatted pull requests.

Automated pull requests fail quality checks or commit linting when project-specific build scripts detect formatting errors, linting violations, or failing tests. Strict adherence to commit linting and scope isolation is enforced before PR creation, preventing non-compliant commits from opening a remote pull request.

Yes, automated PR creation works with existing project-specific build tools and testing scripts. The workflow detects and executes your defined linting, formatting, and testing scripts to validate quality gates, ensuring your code is clean and your pull request is ready for review before remote repository interaction.