Skip to content
Back to skills

Git Pr Workflow

ASecurity

Prepare and submit pull requests with clean history, passing checks, and review-ready context. Use when asked to open, prepare, or finalize a PR.

  • 3 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 11, 2026
code-qualitygogit

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned September 11, 2026

npx -y skills add 0xharryriddle/codex-field-kit --skill git-pr-workflow --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Git Pr Workflow?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Git Pr Workflow
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/0xharryriddle-git-pr-workflow/badge)](https://www.skillsdirectory.com/skills/0xharryriddle-git-pr-workflow)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: git-pr-workflow
description: Prepare and submit pull requests with clean history, passing checks, and review-ready context. Use when asked to open, prepare, or finalize a PR.
---

# Git PR Workflow

Prepare PRs that are easy to review, safe to merge, and fully validated.

## Required Sequence

1. Confirm branch intent and scope.
2. Ensure commits are atomic (`git-atomic-commit`) and messages are conventional (`git-conventional-commit`).
3. Run `git-run-checks` on latest branch state.
4. Rebase or merge mainline according to project policy.
5. Push branch and open PR with a concise summary, test evidence, and risk notes.

## PR Description Checklist

- Problem statement
- What changed and why
- Screenshots/logs when relevant
- Validation performed (commands + outcomes)
- Risks and rollback plan
- Follow-up tasks (if any)

Use `./scripts/pr-checklist.sh` to generate a markdown template.

## Review Readiness Rules

- No unrelated diffs.
- No failing or skipped mandatory checks.
- No unresolved TODOs that hide correctness risk.
- Commit history tells a coherent story.

## Boris-Inspired Operating Rules

- Keep implementation minimal and focused on stated goal.
- Use parallelism only for independent workstreams.
- Verify continuously and surface uncertainty explicitly.

## Claude Mapping (Optional)

- Map this workflow to `/pr-prepare` and `/pr-submit` commands when command files are supported.
- Hook pre-push to run the same check command used in `git-run-checks`.

Files in this skill

  • SKILL.md1.5 KB
  • agents/openai.yaml215 B
  • references/pr-template.md172 B
  • scripts/pr-checklist.sh222 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…