skills.rest
Vincentwei1021
Vincentwei1021COMMUNITY
Explore all skills by this author →
GitHub

pr-workflow

Create branches, submit GitHub pull requests, and merge after CI validation via gh CLI.

29|3|Updated Mar 20, 2026
Search Tags:#git workflow#github#pull requests#gh cli#branch naming#squash merge#ci checks
One-click install
npx skills add https://github.com/Vincentwei1021/Synapse --skill pr-workflow-vincentwei1021
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-workflow
Source: https://github.com/Vincentwei1021/Synapse/tree/main/.claude/skills/pr-workflow
Command: npx skills add https://github.com/Vincentwei1021/Synapse --skill pr-workflow-vincentwei1021

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents stalled or risky pull requests by providing a repeatable workflow to create branches, submit PRs, run CI checks, fix failures, and merge safely.

Core Features & Use Cases

  • Pre-flight validation: verify your working tree before you publish changes.
  • Consistent branch + commit conventions: use clear fix/, feat/, refactor/, test/, docs/, and chore/ prefixes for easier review and history.
  • CI-driven iteration: inspect failed checks via gh, apply targeted fixes, and re-run CI until green before merging.
  • Use Case: When adding a feature or fixing a bug, you can follow the workflow to get reliable test and lint results before asking reviewers to approve the PR.

Quick Start

Tell your AI assistant: "Follow the PR workflow to create a branch, open a PR with a structured summary, check CI results, fix any failures based on the logs, and merge with a squash once approved."

Frequently Asked Questions about pr-workflow

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

FAQPage Schema
How do I automate GitHub pull requests and CI checks using gh cli?▼

You can automate the pull request workflow by using gh cli to open PRs, inspect CI check results, triage failures with targeted commands, and merge safely once approved. This ensures reliable test and lint results before review.

What is the best way to manage git branch naming for features and bugfixes?▼

The best way to manage git branch naming is using consistent prefixes like fix/, feat/, refactor/, test/, docs/, and chore/. This convention provides easier review tracking and cleaner commit history across active repositories.

How do I fix failing CI checks before merging a pull request?▼

To fix failing CI checks, inspect the failed checks via gh cli, apply targeted fixes based on the log output, and re-run CI until the results are green before merging the pull request.

Do I need to run pre-flight checks before opening a GitHub pull request?▼

Yes, you need pre-flight validation to verify your working tree before publishing changes. This prevents stalled or risky pull requests by ensuring your local state is clean and safe.

Can I use squash merge for all types of git workflow changes?▼

Yes, you can use squash merge for features, fixes, refactors, tests, docs, and chores. It provides controlled merge behavior to keep the commit history clean after CI validation passes.

Related Skills

Explore More Software Engineering Skills→
JuanMS20JuanMS20

github-auth

Configure GitHub authentication for Hermes Agent using git, gh CLI, or SSH credentials.

Community
Intermediate
SjdjdiejdrirhdkjejSjdjdiejdrirhdkjej

staging-deployment-phase

Coordinate staging deployments with migrations, health checks, and verification.

Community
Intermediate
baphledbaphled
1

check-compliance

Run linting, formatting, security scans, and tests before committing code.

Community
Intermediate
saif27217saif27217

github

Manage GitHub pull requests and workflow runs via the gh CLI.

Community
Intermediate