skills.rest
guiledo
guiledoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

github-pr-workflow

Automate pull-request and CI/CD workflows with ephemeral branches and conventional commits.

Updated Nov 26, 2025
Search Tags:#workflow#github#pr#ci-cd#code-review#pull-request#git-ops
One-click install
npx skills add https://github.com/guiledo/dotfiles --skill github-pr-workflow-guiledo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/guiledo/dotfiles/tree/main/opencode/.config/opencode/skills/github-pr-workflow
Command: npx skills add https://github.com/guiledo/dotfiles --skill github-pr-workflow-guiledo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, auditable PR/CI workflow to protect the main branch by enforcing ephemeral feature branches, local validation, and semantic commits before merging.

Core Features & Use Cases

  • Ephemeral Branches: Work on feature branches that isolate changes from main.
  • Self-Review & Cleanup: Before committing, review changes and remove debugging artifacts.
  • Local Validation: Run linters, type checks, and tests locally to avoid CI failures.
  • Atomic & Semantic Commits: Use conventional commits for clear history.
  • Create Pull Request: Propose changes with a PR for peer review.

Quick Start

Create an ephemeral feature branch, implement changes, run local checks, and open a pull request for review.

Frequently Asked Questions about github-pr-workflow

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

FAQPage Schema
How do I enforce a safe pull request workflow to protect the main branch?▼

To enforce a safe pull request workflow, use ephemeral feature branches to isolate changes, perform self-review to remove debugging artifacts, run local validation, and open a PR for peer review before merging.

What is the best way to structure commits before opening a pull request?▼

The best way to structure commits before opening a pull request is to use atomic and semantic conventional commits, ensuring a clear, auditable history that satisfies branch hygiene requirements.

How do I prevent CI failures when creating a pull request?▼

To prevent CI failures when creating a pull request, run local validation including linters, type checks, and tests locally on your ephemeral branch before committing and pushing your changes.

Can I use this PR workflow for projects requiring ephemeral branches and conventional commits?▼

Yes, this PR workflow is designed for software projects requiring ephemeral branches, self-review, local validation, and conventional-commit PRs to maintain branch hygiene and an auditable merge process.

Do I need a specific CI/CD platform to automate this pull request workflow?▼

No specific CI/CD platform is required. The workflow automates the pull request process using CLI fallback for robust PR creation, applying to any software project needing safe, auditable merges.

Related Skills

Explore More Software Engineering Skills→
ahandselahandsel
1

git-pull-main

Synchronizes local Git feature branches with the remote main branch.

Community
Intermediate
kevindreekevindree

ci-cd-and-automation

Design and harden CI/CD pipelines with quality gates and deployment automation.

Community
Advanced
bigeasyfreemanbigeasyfreeman
2

ldd-enforcement

Automate linting and syntax checking before testing in TDD workflows.

Community
Intermediate
sakurosakuro
2

merge-pr

Merge GitHub pull requests with the gh CLI after validating CI checks and approvals.

Community
Intermediate