skills.rest
0xharryriddle
0xharryriddleCOMMUNITY
Explore all skills by this author →
𝕏@0xHarryNguyenVNGitHub

git-pr-workflow

Prepare pull requests with atomic commits, conventional messages, and CI checks.

3|Updated Mar 22, 2026
Search Tags:#git#workflow#code-review#branch-management#pull-request#continuous-integration
One-click install
npx skills add https://github.com/0xharryriddle/codex-field-kit --skill git-pr-workflow-0xharryriddle
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-pr-workflow
Source: https://github.com/0xharryriddle/codex-field-kit/tree/main/archive/upstream/chasebuild-agent-skills/git/skills/git-pr-workflow
Command: npx skills add https://github.com/0xharryriddle/codex-field-kit --skill git-pr-workflow-0xharryriddle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

PR workflows can be error-prone and time-consuming. This Skill helps ensure PRs are easy to review, safe to merge, and fully validated.

Core Features & Use Cases

  • Atomic commits with conventional messages to keep history clean
  • Run pre-merge checks and enforce project policy
  • Provide ready-to-review PR descriptions with validation evidence and risk notes

Quick Start

Ask me to prepare a PR for a feature branch; I will run checks, generate a concise PR description, and outline validation evidence.

Frequently Asked Questions about git-pr-workflow

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

FAQPage Schema
How do I prepare a pull request with clean commit history?▼

You prepare a pull request with clean commit history by enforcing atomic commits and conventional messages. This process keeps the branch history readable and the PR ready for code review.

What is the best way to manage branch integration before submitting a PR?▼

Managing branch integration before submitting a PR involves applying a consistent rebasing or merging policy against the mainline. This aligns your branch with the project state before running continuous integration checks.

How do I generate a concise PR description with validation evidence?▼

You generate a concise PR description with validation evidence by running pre-merge checks and compiling the results. This produces a ready-to-review PR complete with a validation checklist and risk notes.

Does this PR workflow support continuous integration checks?▼

Yes, this PR workflow supports continuous integration by running pre-merge checks to enforce project policy. It validates your code across branches and mainline integration before producing the final submission.

Why do I need atomic commits for code review?▼

You need atomic commits for code review to keep your project history clean and focused on single logical changes. This makes the pull request easier to review, safe to merge, and fully validated.

Related Skills

Explore More Software Engineering Skills→
alexanderopalexanderop

using-git-worktrees

Create isolated git worktrees for feature branches with safety checks.

Community
Advanced
QunnnnQunnnn

go-continuous-integration

Configure GitHub Actions CI pipelines for Go projects with testing, linting, and security scanning.

Community
Intermediate
Chang-Shih-YungChang-Shih-Yung

health

Aggregate type checker, linter, and test results into a 0-10 composite score.

Community
Advanced
avvaleavvale

commit-pr

Commit changes, push to a feature branch, and create a GitHub Pull Request.

Official
Advanced