luisdavidtf/git-workflow
skills/git-workflow/SKILL.md
Professional standards for Git version control, branching, and commit messages.
tools
Updated Jun 8, 2026
$ install --global
skillsauthnpx skillsauth add luisdavidtf/vindex git-workflowInstall 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: Jun 8, 2026, 6:09 AM8.2s1 file scanned
SKILL.md
- name:
- git-workflow
- description:
- Professional standards for Git version control, branching, and commit messages.
Git Workflow Standards
Follow these guidelines to maintain a clean, professional history.
1. Commit Messages (Conventional Commits)
Format: type(scope): subject
Types
feat: A new featurefix: A bug fixdocs: Documentation only changesstyle: Changes that do not affect the meaning of the code (white-space, formatting, etc)refactor: A code change that neither fixes a bug nor adds a featureperf: A code change that improves performancetest: Adding missing tests or correcting existing testschore: Changes to the build process or auxiliary tools and libraries such as documentation generation
Example
git commit -m "feat(auth): implement login screen validation"
git commit -m "fix(db): resolve foreign key constraint error in products table"
2. Branching Strategy
main: Production-ready code.develop(Optional): Integration branch.- Feature Branches:
feature/short-description - Bugfix Branches:
fix/short-descriptionorbugfix/short-description
Workflow
- Pull latest changes:
git pull origin main - Create branch:
git checkout -b feature/new-product-card - Work & Commit often.
- Push:
git push origin feature/new-product-card - PR: Create Pull Request with description of changes.
3. Pull Request Template
## Summary
[Brief description of changes]
## Type of Change
- [ ] New feature
- [ ] Bug fix
- [ ] Refactor
## How was this tested?
- [ ] Manual verification
- [ ] Unit tests passed
## Screenshots (if UI change)
[Insert Screenshots]
4. Critical Rules
- NEVER commit secrets (.env files).
- ALWAYS run
npm run lintornpx expo typecheckbefore committing. - SQUASH or REBASE if history is messy before merging (collaborative projects).
Related Skills
luisdavidtf/zustand-store
documentation
VerifiedTrustedCommunity
Guidelines for global state management with Zustand. Trigger: When creating global stores, shared UI state, or managing session data.
SKILL.mdUpdated Jun 8, 2026
luisdavidtf/typescript
development
VerifiedTrustedCommunity
TypeScript strict patterns and best practices. Trigger: When implementing or refactoring TypeScript in .ts/.tsx (types, interfaces, generics, const maps, type guards, removing any, tightening unknown).
SKILL.mdUpdated Jun 8, 2026
luisdavidtf/react-native-style
development
VerifiedTrustedCommunity
Guidelines for styling in React Native (Flexbox, StyleSheet). Trigger: When styling components, fixing layout issues, or adding visual effects.
SKILL.mdUpdated Jun 8, 2026
luisdavidtf/learning-loop
testing
VerifiedTrustedCommunity
Protocol for QA, error verification, and skill evolution to prevent recurring bugs.
SKILL.mdUpdated Jun 8, 2026