metalagman/agent-skills

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.

First seen Feb 21, 2026

Installation

$ npx skills add metalagman/agent-skills --skill github-flow

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from metalagman/agent-skills · top by installs.

npx skills add metalagman/agent-skills

Browse all from metalagman/agent-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 24
Default branch master
Open issues 1
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

More metadata
short-description
Expert guidance on the GitHub Flow branching strategy.

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,693 B
  • docs SUMMARY.md 177 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 35 installs

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

  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.

  • Branch Types & Lifecycles: See [references/branching-model.md](references/branching-model.md).

Developer Policies

  • Upstream Sync, PRs, and Deployment: See [references/policies.md](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](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.