Create a pull request

VerifiedSafe

Concise workflow to prepare a branch, build, test, push, and open a pull request using Gradle.

Sby Skills Guide Bot
DevelopmentBeginner
1010/18/2026
Claude CodeCursorCodex
#git-workflow#pull-request#gradle#commit-conventions#branching

Recommended for

Our review

This skill lays out a seven-step procedure for preparing and opening a pull request on a Gradle project, validating the build and tests before committing.

Strengths

  • Clear ordered checklist from branch creation through to the PR URL
  • Explicit gate: nothing is committed unless ./gradlew build and ./gradlew test pass
  • Enforces a conventional commit message and a PR with a descriptive title and body
  • Reminds the agent not to work directly on main/develop

Limitations

  • Commands are Gradle-specific; the build step must be swapped for other ecosystems
  • Does not explain how the PR is actually created (tooling, remote, authentication) or how to resolve conflicts
  • No branch naming or commit message format conventions are specified
When to use it

Use it when a set of changes is ready and you want them delivered cleanly through a feature branch and a pull request on a Gradle project.

When not to use it

Avoid it on non-Gradle projects, or when the PR must follow a bespoke internal process this skill does not cover.

Security analysis

Safe
Quality score78/100

The skill describes a standard development workflow: creating a branch, running Gradle build and tests, committing, pushing, and opening a PR. It does not instruct destructive actions, data exfiltration, or bypassing safety mechanisms. Running build and test commands is a routine, legitimate activity.

No concerns found

Examples

Open a PR for finished work
My changes are done — create a feature branch if needed, run the build and tests, commit with a conventional message, and open a pull request with a summary.
Ship a bug fix properly
Commit this bug fix on a fix branch, make sure ./gradlew build and ./gradlew test pass first, then push and open a PR for review.
Turn local edits into a pull request
I've made edits on main by mistake — move them to a feature branch, verify the Gradle build and tests, and raise the PR with a descriptive title and body.

Create PR Workflow

  1. Ensure all changes are on a feature/fix branch (create one if on main/develop)
  2. Run the build: ./gradlew build
  3. Run tests: ./gradlew test
  4. If build+tests pass, commit with a conventional commit message
  5. Push the branch
  6. Create a PR with a descriptive title and body summarizing changes
  7. Report the PR URL
Related skills