skills.rest
mukles
muklesCOMMUNITY
Explore all skills by this author →
Website𝕏@mukles_devGitHub

git-commit-push-pr

Automate local changes into pull requests with adaptive descriptions.

Updated Sep 16, 2025
Search Tags:#automation#git#code-review#branch-management#pull-request#pr-description
One-click install
npx skills add https://github.com/mukles/platejs-markdown-converter --skill git-commit-push-pr-mukles
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit-push-pr
Source: https://github.com/mukles/platejs-markdown-converter/tree/main/.agents/skills/git-commit-push-pr
Command: npx skills add https://github.com/mukles/platejs-markdown-converter --skill git-commit-push-pr-mukles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts in-progress changes into a ready-to-open pull request by automatically generating a PR description that scales with the change's complexity and guiding the full PR workflow from commit to merge.

Core Features & Use Cases

  • Generate adaptive PR descriptions that reflect the scope and impact of the changes.
  • Detect existing PRs for the current branch and update descriptions or create new PRs as needed.
  • Manage branch naming, remote/base detection, and PR creation to streamline end-to-end PR workflows.

Quick Start

Tell me to commit the changes, push them, and open a PR with a value-focused description for the current branch.

Frequently Asked Questions about git-commit-push-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a pull request description that reflects the scope of my code changes?▼

To generate a pull request description, this Skill automates turning local changes into a ready-to-review PR with an adaptive, value-first description. It scales with the change's complexity to properly convey intent, scope, and impact following repository conventions.

Can I update an existing PR description automatically when I push new commits?▼

Yes, you can update an existing PR description automatically. The Skill detects existing PRs for the current branch and updates descriptions or creates new PRs as needed, streamlining the end-to-end workflow from commit to merge.

How do I automate git commit, push, and branch management for a new pull request?▼

Automating git commit, push, and branch management is achieved by guiding the full PR workflow. The Skill handles branch naming, remote/base detection, and PR creation to convert in-progress changes into a ready-to-open pull request.

Does this PR automation work for both small fixes and large feature work?▼

Yes, this PR automation works for both small fixes and large feature work. It applies to software projects of varying sizes, generating adaptive PR descriptions that scale with the change's complexity and accurately convey impact.

What's the best way to manage branch naming and remote base detection for pull requests?▼

The best way to manage branch naming and remote base detection is through automated PR creation workflows. This Skill satisfies base/remote detection and branch naming automatically, following repository conventions and best practices.

Why do my pull request descriptions fail to convey the intent and impact of my changes?▼

Pull request descriptions often fail to convey intent when they are not value-driven. This Skill solves that by generating adaptive, value-first descriptions that scale with the change's complexity to clearly communicate the scope and impact.

Related Skills

Explore More Software Engineering Skills→
mhattingpetemhattingpete
657

git-pushing

Stage, commit, and push code changes with conventional commit messages.

Community
Basic
zach-sourcezach-source

ci-polling

Monitor GitHub Actions and GitLab CI/CD pipeline statuses with background polling tasks.

Community
Intermediate
webdevtodayjasonwebdevtodayjason

requesting-code-review

Review code quality with static analysis and security scans before commits.

Community
Advanced
andrew-t-jamesandrew-t-james

pr-create

Stage changes, create conventional commits, push with force-with-lease, and open a pull request via gh CLI.

Community
Intermediate