skills.rest
ammonfife
ammonfifeCOMMUNITY
Explore all skills by this author →
GitHub

pr-workflow

Automates pull request management with guidelines for commits, CI, dependencies, and security.

Updated Feb 10, 2026
Search Tags:#CI/CD#security guidelines#PR management#platform-specific#commit practices
One-click install
npx skills add https://github.com/ammonfife/sakima.co --skill pr-workflow-ammonfife
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-workflow
Source: https://github.com/ammonfife/sakima.co/tree/main/.claude/skills/turso-pr-workflow
Command: npx skills add https://github.com/ammonfife/sakima.co --skill pr-workflow-ammonfife

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a standardized PR workflow with guidelines for commits, formatting, CI, dependencies, and security, tailored for different platforms.

Core Features & Use Cases

  • Platform-Specific Guidelines: Offers specific instructions for Claude Code, OpenClaw, Gemini, and Codex.
  • Commit Practices: Emphasizes atomic commits, clear commit messages, and the use of git rebase -i.
  • PR Guidelines: Focuses on focused PRs, test runs, and maintaining a narrative with commits.

Quick Start

To execute the PR workflow for Claude Code, follow the guidelines for targeted edits and background task spawning.

Frequently Asked Questions about pr-workflow

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

FAQPage Schema
How do I automate pull request management across different coding platforms?▼

Automating pull request workflows requires standardized guidelines for commits, CI, dependency management, and security. This skill provides platform-specific instructions for Claude Code, OpenClaw, Gemini, and Codex to standardize the process.

What is the best way to maintain a clear commit history in pull requests?▼

Maintaining a clear commit history in pull requests involves using atomic commits and clear commit messages. Utilizing interactive rebase ensures commits maintain a logical narrative before merging.

Do I need specific CI configurations to enforce PR security guidelines?▼

Enforcing PR security guidelines requires continuous integration checks for dependency management and formatting. The workflow establishes these security and CI parameters to ensure focused, tested pull requests.

Can I use these PR guidelines with Gemini and Codex environments?▼

Yes, these PR guidelines are designed for use across various platforms including Gemini and Codex. They offer platform-specific instructions to ensure effective pull request management within those environments.

Why should I use a standardized PR workflow instead of ad-hoc commit practices?▼

A standardized PR workflow ensures consistent commit formatting, security checks, and dependency management across teams. Ad-hoc commit practices often lack enforced CI guidelines, leading to fragmented pull request narratives.

When should I use interactive rebase in my pull request workflow?▼

You should use interactive rebase in your pull request workflow to squash or reorder commits before merging. This ensures your pull request maintains a focused, understandable narrative with atomic commits.

Related Skills

Explore More Software Engineering Skills→
darknightdarknight
1

ci

Commit staged Git changes after passing lint checks.

Community
Intermediate
app-vitalsapp-vitals
9

repo-config

Configure branch protection, required checks, secrets, and deploy hooks for merge gates.

Official
Advanced
williamzujkowskiwilliamzujkowski
17

microservices-patterns

Identify security vulnerabilities from missing security patterns in microservices environments.

Community
Advanced
RamblurrRamblurr

Finishing a Development Branch

Verifies tests, formatting, and linting before creating a Pull Request.

Community
Intermediate