the-own-lab/git-ops
skills/git-ops/SKILL.md
Git branch, commit, and merge operations following project conventions. Use for all git workflow actions.
tools
Updated Apr 21, 2026
$ install --global
skillsauthnpx skillsauth add the-own-lab/Claude-company-of-one git-opsInstall 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:04 PM12.3s1 file scanned
SKILL.md
- name:
- git-ops
- description:
- Git branch, commit, and merge operations following project conventions. Use for all git workflow actions.
Git Operations
Standardized git workflow for branch management, commits, and merges.
Branch Naming
Use the following prefixes based on the type of work:
| Prefix | Purpose |
| ----------- | ------------------------------------------ |
| feature/ | New functionality |
| fix/ | Bug fixes |
| refactor/ | Code restructuring without behavior change |
| docs/ | Documentation updates |
| chore/ | Maintenance, tooling, dependency updates |
Branch names should be lowercase, hyphen-separated, and descriptive:
feature/add-user-authentication, fix/null-pointer-in-parser
Commit Convention
Follow the conventional commit format:
type(scope): description
Optional body with additional context.
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Types: feat, fix, refactor, docs, test, chore, perf, ci
Rules:
- Description is lowercase, imperative mood, no trailing period
- Scope is optional but encouraged for clarity
- Body explains "why" not "what" when the change is non-obvious
- Every commit includes the Co-Authored-By line
Merge Workflow
- Verify all tests pass on the branch
- Ensure the branch is up to date with the target branch
- Squash merge to keep history clean
- Delete the feature branch after merge
- Confirm a clean worktree after merge completes
Safety Rules
- Never force-push to the default branch (main/master)
- Never delete the default branch
- Always verify tests pass before merging
- Always review the diff before committing
- Never commit files containing secrets or credentials
- Prefer creating new commits over amending existing ones
- Review
.gitignorewhen adding new file types - Tag releases with semantic versioning (vX.Y.Z)
Related Skills
the-own-lab/write-brief
documentation
VerifiedTrustedCommunity
Update BRIEF.md sections during a command run. Any skill that produces a brief-persisted artifact calls this to write it back.
SKILL.mdUpdated Apr 22, 2026
the-own-lab/verify
development
VerifiedTrustedCommunity
Post-code check: run tests + confirm TODO acceptance items map to passing tests; applies a security lens but is not a separate scan.
SKILL.mdUpdated Apr 22, 2026
the-own-lab/update-docs
documentation
VerifiedTrustedCommunity
Command post-step: write CHANGELOG + TODO once per command run. One call, not per-skill doc writes.
SKILL.mdUpdated Apr 22, 2026
the-own-lab/spec-writing
content-media
VerifiedTrustedCommunity
Author REQUIREMENTS.md + DESIGN.md + TODO.md for a feature. The three files are one contract; they ship together.
SKILL.mdUpdated Apr 22, 2026