skills.rest
p-o-ke-nae
p-o-ke-naeCOMMUNITY
Explore all skills by this author →
GitHub

github-flow

Guide GitHub Flow branching, commits, testing, pull requests, and squash merges.

Updated May 16, 2026
Search Tags:#code review#conventional commits#branching#pull requests#squash merge#github flow
One-click install
npx skills add https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory --skill github-flow-p-o-ke-nae
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-flow
Source: https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory/tree/main/.github/skills/github-flow
Command: npx skills add https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory --skill github-flow-p-o-ke-nae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents ad hoc code changes by enforcing a consistent GitHub Flow process for branching, committing, testing, reviewing, and merging in this repository.

Core Features & Use Cases

  • Branch Discipline: Creates feature branches from main instead of committing directly to protected branches.
  • Commit and PR Standards: Uses Conventional Commits and Draft Pull Requests to keep history and reviews consistent.
  • Quality Gates: Requires local build and test checks before review and merge.
  • Merge Workflow: Guides the final review, Ready for Review transition, Squash Merge, and branch cleanup.
  • Use Case: When implementing a bug fix or feature, this Skill helps you move from an issue-specific branch to a reviewed PR and clean main-branch integration without missing process steps.

Quick Start

Ask the assistant to help you follow this repository’s GitHub Flow for your change, from creating the correct feature branch through testing, drafting the pull request, review, and squash merge.

Frequently Asked Questions about github-flow

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

FAQPage Schema
What is GitHub Flow and how does it manage branch-to-merge workflows?▼

GitHub Flow is a branch-to-merge workflow that standardizes code changes by guiding branching, Conventional Commits, local testing, Draft Pull Requests, reviewer approval, and squash merge execution.

How do I create a pull request using GitHub Flow for a feature branch?▼

To create a pull request using GitHub Flow, branch from main, validate local build and test checks, commit conventionally, then create a Draft Pull Request for reviewer approval before transitioning to Ready for Review.

Does GitHub Flow require conventional commits and local testing before review?▼

Yes, GitHub Flow requires Conventional Commits for history consistency and local build and test validation as quality gates before transitioning a Draft Pull Request to Ready for Review.

What's the best way to handle branch cleanup after a squash merge in GitHub Flow?▼

The best way to handle branch cleanup after a squash merge in GitHub Flow is to execute the merge into the protected main-branch and then delete the feature branch to keep the repository clean.

Can I commit directly to a protected main-branch when using GitHub Flow?▼

No, GitHub Flow prevents ad hoc code changes by enforcing branch discipline, requiring you to create feature branches from main instead of committing directly to protected branches.

Related Skills

Explore More Software Engineering Skills→
yharuto0917yharuto0917

pr-creator

Create pull requests with repository templates and branch safety checks.

Community
Advanced
doravidandoravidan

ralph-merge

Merge RALPH worktree changes into the main branch with optional squash.

Community
Basic
lepahclepahc
1

kspec-merge

Merge approved Git task branches into integration branches with kspec review gates.

Official
Intermediate
legioncodeinclegioncodeinc
72

branching-strategy-stinger

Recommend Git branching workflows to reduce merge conflicts.

Official
Advanced