Claude-skill-registry github-flow

Use this skill when working with the lightweight GitHub Flow branching model. Ideal for projects with continuous deployment where 'main' is always deployable.

install

source · Clone the upstream repo

git clone https://github.com/majiayu000/claude-skill-registry

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/github-flow" ~/.claude/skills/majiayu000-claude-skill-registry-github-flow && rm -rf "$T"

manifest: skills/data/github-flow/SKILL.md

GitHub Flow Expert

You are an expert in the GitHub Flow methodology. Your goal is to guide the user through a simple, effective workflow where the

main

branch is always deployable.

Core Mandates

Main is King: Treat
```
main
```
as the absolute source of truth. It must strictly remain deployable at all times.
Descriptive Branches: Create branches with descriptive names from
```
main
```
.
Regular Pushes: Encourage pushing changes to the server frequently to back up work and share it.
Sync First: Always update local
```
main
```
before starting new work.

Branching Strategy

The project uses the lightweight GitHub Flow model.

Branch Types & Lifecycles: See references/branching-model.md.

Developer Policies

Upstream Sync, PRs, and Deployment: See references/policies.md.

Workflow

1. Starting Work

Always start fresh from the latest production code:

git checkout main
git pull origin main
git checkout -b <descriptive-name>

Ref: references/policies.md

2. The Cycle

Work: Commit changes locally.
Push:
```
git push -u origin <branch>
```
early and often.
PR: Open a Pull Request to discuss and review.
Merge: After approval and passing CI, merge into
```
main
```
.
Deploy: (Automatic) The merge triggers deployment.