skills.rest
ravenoak
ravenoakCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

github-flow

Enforce GitHub Flow with feature branches, atomic commits, and CI-gated PR merges.

Updated Apr 27, 2026
Search Tags:#git#workflow#github#branching#code-review#pull-request#merges
One-click install
npx skills add https://github.com/ravenoak/oh-my-stigmergy --skill github-flow-ravenoak
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-flow
Source: https://github.com/ravenoak/oh-my-stigmergy/tree/main/.cursor/skills/github-flow
Command: npx skills add https://github.com/ravenoak/oh-my-stigmergy --skill github-flow-ravenoak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub Flow standardizes how code is proposed, reviewed, and merged to ensure traceable history, predictable releases, and reduced integration risk.

Core Features & Use Cases

  • Feature-branch from main for all new work
  • Atomic commits with concise messages
  • PR-only integration gated by CI checks
  • Linear main history via squash or rebase merges

Quick Start

Create a feature branch from main, implement changes atomically, and open a PR for CI checks and merging.

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 feature branching?▼

GitHub Flow is a branching strategy that requires creating feature branches from main, making atomic commits, and integrating changes exclusively through pull requests to ensure traceable history and predictable releases.

How do I enforce CI checks before merging a pull request into main?▼

You can enforce CI checks before merging a pull request by gating merges behind continuous integration validations, ensuring only reviewed and passing code integrates into the main branch.

Does GitHub Flow support squash or rebase merges for linear history?▼

Yes, GitHub Flow supports linear main history by using squash or rebase merges, which consolidates feature branch commits into a single, traceable commit on the main branch during integration.

Why should I use atomic commits in my feature branch workflow?▼

Atomic commits in your feature branch workflow isolate distinct logical changes with concise messages, creating a clean, auditable history that reduces integration risk and ensures traceable code modifications.

Can I integrate code directly into main without opening a pull request?▼

No, this GitHub Flow approach uses PR-only integration, meaning all new work from feature branches must pass through a pull request for code review and CI gating before reaching the main branch.

What's the best way to maintain a clean git history when using GitHub Flow?▼

The best way to maintain a clean git history is to branch from main, commit changes atomically with concise messages, and use squash or rebase merges when integrating pull requests back into the main branch.

Related Skills

Explore More Software Engineering Skills→
Tx1207Tx1207
5

project-creator

Create a new project from a template, initialize uv, and configure a local Git repository.

Community
Advanced
tachiiri-orgtachiiri-org

release

Create a pull request from the dev branch to main after verifying branch and remote state.

Official
Intermediate
heyallencaoheyallencao
118

ks-verify

Run automated test suites and coverage checks to validate code claims.

Community
Intermediate
oscardlfroscardlfr
1

git-flow

Automate Git Flow branch management for features, releases, and hotfixes.

Community
Intermediate