git-commit-push-pr

To automatically generate a pull request description, this skill reads your uncommitted changes and current branch state, then creates value-focused PR titles and bodies aligned with project conventions. It handles committing, pushing, and PR creation in a safe sequence.

Yes, you can update an existing PR description when pushing new commits. The workflow detects an open PR for the current branch and augments or updates its title and body to reflect the latest scope, intent, and design decisions.

The best way to automate local changes into a GitHub pull request is using a workflow that handles branching, committing, pushing, and PR creation with adaptive descriptions. This skill applies robust guardrails and error handling throughout the sequence.

Yes, you need GitHub repository access and a local Git repository to automate PR creation. The workflow requires reading the current branch, uncommitted changes, and PR state to generate or update PR text according to project conventions.

Adaptive PR text generation handles varying complexity by scaling value-first descriptions according to the change's scope. It reads uncommitted changes and PR state to produce titles and bodies that reflect design decisions and intent.

Using an automated workflow for branching, committing, and pushing ensures a safe, auditable sequence with robust error handling. It transforms local changes into a pull request with adaptive descriptions, reducing manual overhead and enforcing project conventions.