channinghe/git-workflow
claude/skills/git-workflow/SKILL.md
Git workflow standards. Apply when committing changes, creating pull requests, or managing branches.
tools
Updated May 8, 2026
$ install --global
skillsauthnpx skillsauth add channinghe/dotfiles 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: May 8, 2026, 3:36 AM347.3s1 file scanned
SKILL.md
- name:
- git-workflow
- description:
- Git workflow standards. Apply when committing changes, creating pull requests, or managing branches.
Git Workflow Standards
Commit Message Format
Follow Conventional Commits strictly:
<type>(<scope>): <subject>
<body>
<footer>
Types:
feat: New featurefix: Bug fixrefactor: Code change without fixing bug or adding featureperf: Performance improvementtest: Adding or updating testsdocs: Documentation changesstyle: Code style changes (formatting, etc.)chore: Maintenance tasks
Examples:
feat(auth): add OAuth2 login flow
Implements authorization code flow with PKCE.
Supports Google and GitHub providers.
Closes #123
fix(payment): handle Stripe webhook retries
Previous implementation didn't handle duplicate
webhook events, causing duplicate charge attempts.
Fixes #456
Commit Rules
- Subject line max 50 chars
- Imperative mood: "Add feature" not "Added feature" or "Adds feature"
- No period at end of subject
- Body explains WHY, not WHAT (code shows what)
- Reference issues: Use
Closes #123orRefs #456
Branch Strategy
main (protected)
├─ feature/<feature-name>
├─ fix/<bug-description>
├─ hotfix/<urgent-fix>
└─ refactor/<description>
Rules:
- main: Only via merge PR, direct push forbidden
- feature branches: Delete after merge
- branch naming: Lowercase, kebab-case, descriptive
- branch lifespan: Max 2 weeks, else split or abandon
Pull Request Standards
PR Title
Follow commit format, include PR number:
feat(auth): add OAuth2 login flow (#42)
PR Description Template
## Summary
[Bullet points, 2-3 lines max]
## Changes
- File A: What changed
- File B: What changed
## Test Plan
- [ ] Unit tests pass
- [ ] Integration tests pass
- [ ] Manual testing done
## Breaking Changes
[List any breaking changes or "None"]
## Screenshots (if applicable)
PR Review Rules
- At least 1 reviewer approval before merge
- All checks must pass (CI/CD, tests, linting)
- Address all review comments before requesting re-review
- Squash commits when merging to main
Git Best Practices
- Amend only: If commit not pushed, use
--amendto fix typos - Never force push to main
- Use .gitignore religiously: Never commit:
.env,.env.localnode_modules/,dist/,build/- IDE files (
.vscode/,.idea/) - OS files (
.DS_Store,Thumbs.db)
- Rebase before PR: Keep branch up-to-date with main
- Atomic commits: Each commit should be a logical unit, can be reverted independently
Related Skills
channinghe/web-design-guidelines
development
VerifiedTrustedCommunity
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
SKILL.mdUpdated May 8, 2026
channinghe/claude/skills/verification-loop
development
VerifiedTrustedCommunity
# Verification Loop Skill A comprehensive verification system for Claude Code sessions. ## When to Use Invoke this skill: - After completing a feature or significant code change - Before creating a PR - When you want to ensure quality gates pass - After refactoring ## Verification Phases ### Phase 1: Build Verification ```bash # Check if project builds npm run build 2>&1 | tail -20 # OR pnpm build 2>&1 | tail -20 ``` If build fails, STOP and fix before continuing. ### Phase 2: Type Check
SKILL.mdUpdated May 8, 2026
channinghe/tooling
tools
VerifiedTrustedCommunity
Tooling and verification. Apply when encountering unfamiliar third-party libraries, framework updates, uncertain parameter types, verifying best practices, or uncertain API parameters.
SKILL.mdUpdated May 8, 2026
channinghe/tdd-workflow
development
VerifiedTrustedCommunity
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
SKILL.mdUpdated May 8, 2026