skills.rest
darknight
darknightCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pr

Automates GitHub pull requests from committed code changes using gh CLI and Conventional Commits style titles.

1|Updated Jan 8, 2026
Search Tags:#automation#git#commit#github#pr#lint#pull-request
One-click install
npx skills add https://github.com/darknight/cc-deck --skill pr-darknight
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/darknight/cc-deck/tree/main/plugins/deck/skills/pr
Command: npx skills add https://github.com/darknight/cc-deck --skill pr-darknight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically create GitHub pull requests from code changes by linting, formatting, committing, and pushing them, reducing manual steps and human error.

Core Features & Use Cases

  • End-to-end PR automation: detect the current branch, ensure changes are committed, and open a PR against main with a descriptive message.
  • Linting and formatting: run checks before committing to maintain code quality.
  • PR creation via gh CLI: generate a conventional-commits-style title and open the PR, returning the PR URL.

Quick Start

Trigger the PR workflow on your current branch to lint, commit, push, and open a PR to main.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I automate creating a GitHub pull request from local code changes?▼

To automate creating a GitHub pull request, trigger the workflow to lint, format, commit, and push changes, then generate a conventional-commits-style title and open the PR against the main branch using the gh CLI.

Can I automatically enforce conventional commits when pushing a new pull request?▼

Yes, the workflow enforces conventional commits by applying one-line commit messages and generating a concise conventional-commits-style title for the pull request opened through the gh CLI.

Does the pull request automation workflow skip untracked files in my git branch?▼

Yes, the workflow skips untracked files, detects the current branch, and ensures only tracked code changes are linted, formatted, committed, and pushed before opening the PR against main.

What is the best way to lint and format code before opening a pull request to main?▼

The best way to lint and format code before opening a pull request to main is triggering an end-to-end workflow that runs checks, commits with a one-line message, pushes, and opens the PR via the gh CLI.

Do I need the gh CLI installed to automate GitHub PR creation from my branch?▼

Yes, you need the gh CLI installed because the automation uses it to open the pull request against main and return the PR URL after committing and pushing your code changes.

Why does my automated pull request workflow default to the main branch?▼

The automated pull request workflow defaults to the main branch because the end-to-end PR creation process is designed to open pull requests against main from your current detected branch using the gh CLI.

Related Skills

Explore More Software Engineering Skills→
Sir-chawakornSir-chawakorn
9

git-commit-pr

Stage code changes and generate Conventional Commits messages from git diffs.

Community
Advanced
levkisslevkiss

github

Manage GitHub repositories via GitHub CLI for commits, branches, pull requests, issues, releases, and Pages deployment.

Community
Advanced
mlflowmlflow
1

add-review-comment

Post review comments to GitHub pull requests via the GitHub CLI.

Official
Intermediate
cpfcoachingcpfcoaching

openai-yeet

Automate GitHub pull request creation by staging, committing, and pushing changes.

Community
Intermediate