hoangnguyen0403/common-git-collaboration
skills/common/common-git-collaboration/SKILL.md
Enforce version control best practices for commits, branching, pull requests, and repository security. Use when writing commits, creating branches, merging, or opening pull requests.
$ install --global
skillsauthnpx skillsauth add hoangnguyen0403/agent-skills-standard common-git-collaborationInstall 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: Jul 15, 2026, 3:23 AM120.2s4 files scanned
SKILL.md
- name:
- common-git-collaboration
- description:
- Enforce version control best practices for commits, branching, pull requests, and repository security. Use when writing commits, creating branches, merging, or opening pull requests.
Git & Collaboration
Priority: P0 (CRITICAL)
1. Write Conventional Commits
- Format:
<type>(<scope>): <description>(e.g.,feat(auth): add login validation). - Types:
feat,fix,docs,style,refactor,perf,test,chore. - Use imperative mood: "add feature" not "added feature".
- One commit = one logical change — no mega-commits.
See implementation examples for conventional commit examples.
2. Manage Branches
- Name with prefixes:
feat/,fix/,hotfix/,refactor/,docs/. - Create new branch for every task to keep main stable and deployable.
- Never push directly to
mainordevelop— use Pull Requests. - Pull before you push to resolve conflicts locally.
- Prefer
git rebaseover merge for linear history on feature branches. - Use
git rebase -ito squash messy commits before pushing.
3. Submit Quality Pull Requests
- Limit to < 300 lines of code for effective review.
- State what changed, why, and how to test. Link issues (
Closes #123). - Self-review for obvious errors before requesting peers.
- PRs must pass all CI checks (lint, test, build) before merging.
4. Protect Secrets and Metadata
- Never commit
.env, keys, or certificates — use.gitignorestrictly. - Use
huskyorlefthookfor local Git Hooks enforcement. - Tag releases with SemVer (
vX.Y.Z) and updateCHANGELOG.md.
Anti-Patterns
- No direct push to main: All changes via PR, no exceptions.
- No mega-commits: One commit = one logical change. Split large ones.
- No secrets in history: Use
git filter-repoto purge; rotate secret.
References
- Clean Linear History & Rebase Examples
Related Skills
hoangnguyen0403/common-operator-profile
testing
VerifiedTrustedCommunity
Infer the requesting operator's technical fluency from message content (never ask directly) and adapt register — business, hybrid, or technical — across SDLC workflow output. Use when starting sdlc, brainstorm-feature, plan-feature, verify-work, publish-notes, or session-report, or whenever a request's phrasing signals a non-technical or cross-stack operator.
524SKILL.mdUpdated Jul 12, 2026
hoangnguyen0403/database-transactions
documentation
VerifiedTrustedCommunity
Define transaction boundaries, locking, and consistency guarantees for multi-step writes. Use when designing atomic operations, retries, idempotency, or concurrent write behavior.
524SKILL.mdUpdated Jun 19, 2026
hoangnguyen0403/database-schema-design
development
VerifiedTrustedCommunity
Design relational or document schemas from access patterns, cardinality, and lifecycle. Use when modeling entities, choosing embed vs normalize, or shaping schema boundaries before implementation.
524SKILL.mdUpdated Jun 19, 2026
hoangnguyen0403/database-query-performance
data-ai
VerifiedTrustedCommunity
Diagnose database latency with explain plans, index ownership, and query-shape review. Use when a query is slow, an index is missing, or scans and N+1 patterns appear.
524SKILL.mdUpdated Jun 19, 2026