mcpField
G
github-flow

github-flow

github.com/metalagmanDevelopment2640 installsUpdated 10w ago
Repository

About github-flow

A coding skill that guides developers through GitHub Flow, keeping `main` deployable while work moves through branches, pushes, pull requests, and merges. It emphasizes starting from an up-to-date `main` and pushing changes regularly.

Key features

  1. 01Deployable `main` branch
  2. 02Descriptive work branches
  3. 03Frequent remote pushes
  4. 04Pull request review cycle
  5. 05Deployment after merge

Use cases

  1. 01Starting work from current `main`
  2. 02Backing up ongoing branch work
  3. 03Reviewing changes before merging

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/metalagman/agent-skills --skill github-flow

After installing, type/github-flowin Claude Code to confirm it loaded.

Bundled filesreferences/branching-model.mdreferences/policies.md

Details

From the project README

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

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

Branching Strategy

The project uses the lightweight GitHub Flow model.

Developer Policies

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
  1. Work: Commit changes locally.
  2. Push: git push -u origin <branch> early and often.
  3. PR: Open a Pull Request to discuss and review.
  4. Merge: After approval and passing CI, merge into main.
  5. Deploy: (Automatic) The merge triggers deployment.

Comments

Markdown supported