Agent skill
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 this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/github-flow
Metadata
Additional technical details for this skill
- short description
- Expert guidance on the GitHub Flow branching strategy.
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
mainas 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
mainbefore 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.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?