mosesgameli/git-flow
.agents/skills/git-flow/SKILL.md
A structured methodology for managing version control, remotes, and pull requests within the ZTVS repository.
$ install --global
skillsauthnpx skillsauth add mosesgameli/ztvs git-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: Apr 16, 2026, 10:43 PM26.3s1 file scanned
SKILL.md
- name:
- git-flow
- description:
- A structured methodology for managing version control, remotes, and pull requests within the ZTVS repository.
Skill: Git Flow for ZTVS
This skill provides a structured methodology for managing version control, remotes, and pull requests within the Zero Trust Vulnerability Scanner (ZTVS) repository.
Overview
ZTVS standardizes on GitHub-based collaboration. The primary delivery mechanism is the Pull Request (PR).
🛠️ Step-by-Step Implementation
1. Branching Strategy
Always create a fresh branch for new work.
- Use the conventional naming:
feat/<name>,fix/<name>, ordocs/<name>. - Command:
git checkout -b feat/my-new-feature
2. Committing Work
Follow the Conventional Commits rules.
- Workflow: Use the
/gitworkflow to stage and commit. - Command:
git commit -m "feat(plugin): add network check"
3. Pushing & Remotes
- Workflow: Use the
/gitworkflow to push to your target remote. - Identifying remotes:
git remote -v. - Important: Code MUST be pushed to a remote branch before a Pull Request can be created.
4. PR Creation via gh
Automate the pull request lifecycle using the GitHub CLI once your code is pushed:
- Workflow: Use the
/prworkflow to create and view Pull Requests. - Command:
gh pr create --base main --head <current-branch> --title "feat: my change" --body "Detailed description" - Link to RFCs if applicable:
Depends on RFC-001.
5. Keeping Main Up-to-Date
- Checkout main:
git checkout main - Pull latest:
git pull <remote> main - Rebase your feature branch:
git checkout feat/my-feature && git rebase main
🛡️ Best Practices
- Atomic Commits: Keep each commit focused on one logical change.
- DCO/Signing: If required, use
git commit -sfor Developer Certificate of Origin. - Squash-on-Merge: Prefer squashing commits into a single descriptive commit upon PR merge to keep the
mainhistory linear and clean.
Related Skills
mosesgameli/pr-flow
tools
VerifiedTrustedCommunity
Create, view, and manage Pull Requests on GitHub.
4SKILL.mdUpdated Apr 16, 2026
mosesgameli/plugin-dev
tools
VerifiedTrustedCommunity
A skill for developing and integrating new vulnerability scanning plugins for the Zero Trust Vulnerability Scanner (ZTVS).
4SKILL.mdUpdated Apr 16, 2026
mosesgameli/open-source-compliance
development
VerifiedTrustedCommunity
Consolidates the standards for professional, gold-standard open-source development.
4SKILL.mdUpdated Apr 16, 2026
openclaw/taskflow
tools
VerifiedTrustedCommunity
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
357,764SKILL.mdUpdated Apr 10, 2026