github-pr-push

Push code changes and create or update GitHub Pull Requests with automated checks.

Updated Sep 12, 2023
One-click install
npx skills add https://github.com/byunghak-dable/.dotfiles --skill github-pr-push
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr-push
Source: https://github.com/byunghak-dable/.dotfiles/tree/main/claude/.claude/skills/github-pr-push
Command: npx skills add https://github.com/byunghak-dable/.dotfiles --skill github-pr-push

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of pushing code changes to a branch and creating or updating a GitHub Pull Request, including pre-push checks and intelligent assignment of reviewers and labels.

Core Features & Use Cases

  • Automated Pre-push Checks: Runs linters and type checkers on changed files before pushing.
  • Code Review Assistance: Provides a structured review of branch changes and prompts for README updates.
  • Intelligent PR Creation/Update: Automatically creates a new PR or updates an existing one, inferring titles, bodies, assignees, and labels based on branch naming conventions and commit messages.
  • Use Case: After completing a new feature, you can run this Skill to automatically push your code, ensure it passes linting, review the changes, and create a well-formatted PR with appropriate labels and assignees, all with minimal manual intervention.

Quick Start

Push the current branch and create or update a GitHub Pull Request with automated checks and intelligent metadata.

Frequently Asked Questions about github-pr-push

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

FAQPage Schema
How do I automate GitHub pull request creation with linting and code review?

You can automate GitHub pull request creation by running a script that pushes code changes to a remote branch, performs pre-push static analysis like linting and type checking, and generates PR titles, bodies, assignees, and labels automatically.

Can I automatically assign reviewers and labels to a GitHub PR based on branch naming?

Yes, you can automatically assign reviewers and labels by inferring metadata from branch naming conventions and commit history, allowing the PR creation process to intelligently populate assignees and labels without manual input.

Does this automated PR workflow run static analysis before pushing to the remote branch?

Yes, the automated PR workflow runs static analysis before pushing, executing linters and type checkers on changed files to ensure code quality standards are met prior to remote branch updates.

How do I update an existing GitHub pull request with new code changes and metadata?

You can update an existing GitHub pull request by pushing new code changes to the same remote branch, which triggers the workflow to refresh the PR body, update labels, and run code review assistance based on the latest commit history.

What is the best way to streamline code review and README updates during PR creation?

The best way to streamline code review during PR creation is to use an automated workflow that provides a structured review of branch changes and prompts for README updates before finalizing the pull request.

Do I need external dependencies to automate linting and type checking for GitHub PRs?

No external dependencies are required to automate linting and type checking for GitHub PRs, as the workflow operates independently using internal scripts to perform pre-push static analysis and code review.