metalagman/github-flow
github-flow/SKILL.md
Use this skill when working with the lightweight GitHub Flow branching model. Ideal for projects with continuous deployment where 'main' is always deployable.
$ install --global
skillsauthnpx skillsauth add metalagman/agent-skills github-flowInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 7, 2026, 6:20 AM209.3s3 files scanned
SKILL.md
- name:
- github-flow
- description:
- Use this skill when working with the lightweight GitHub Flow branching model. Ideal for projects with continuous deployment where 'main' is always deployable.
- short-description:
- Expert guidance on the GitHub Flow branching strategy.
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.
Related Skills
metalagman/skill-writer
development
VerifiedTrustedCommunity
Use this skill to design, document, and structure AI agent skills for Gemini, Claude, and Codex. It provides architectural rules, directory standards, and writing best practices.
13SKILL.mdUpdated May 7, 2026
metalagman/omnidist
development
VerifiedTrustedCommunity
Use this skill to initialize, configure, and run omnidist release workflows for Go projects (`init`, `ci`, `build`, `stage`, `verify`, `publish`) including npm and uv publishing setup.
13SKILL.mdUpdated May 7, 2026
metalagman/golangci-lint-strict
development
VerifiedTrustedCommunity
Use this skill to install and use the upstream powerman/golangci-lint-strict config for an exact golangci-lint version by fetching the versioned config file unchanged.
13SKILL.mdUpdated May 7, 2026
metalagman/go-uber-style-guide
development
VerifiedTrustedCommunity
Use this skill to write, refactor, or review Go code according to the Uber Go Style Guide. It ensures strict adherence to correctness, safety, and idiomatic patterns.
13SKILL.mdUpdated May 7, 2026