scruffydan/git-push
source/skills/git-push/SKILL.md
You MUST use this when performing a git push. Pre-push checklist for README updates, tests/linters, commit hygiene, secret scanning, and branch/remote status. Use when preparing to run git push, reviewing a branch before publishing, or verifying release readiness.
development
Updated May 4, 2026
$ install --global
skillsauthnpx skillsauth add scruffydan/AI-Agents git-pushInstall 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 4, 2026, 4:12 AM208.0s1 file scanned
SKILL.md
- name:
- git-push
- description:
- You MUST use this when performing a git push. Pre-push checklist for README updates, tests/linters, commit hygiene, secret scanning, and branch/remote status. Use when preparing to run git push, reviewing a branch before publishing, or verifying release readiness.
Git Push Checklist
Systematic checks to perform before pushing code to remote repositories.
Pre-Push Verification
1. README Update Check
CRITICAL: Verify README is current with changes
Before pushing, check if README needs updates:
# Check if README exists
ls -la README.md 2>/dev/null
Update README if:
- New features, commands, or configuration changes
- Installation, dependencies, or requirements change
- Breaking changes or API changes
2. Commit Quality
Review commit messages:
git log origin/main..HEAD --oneline
Ensure commits:
- Follow conventional commits format (feat:, fix:, docs:, etc.)
- Have descriptive messages explaining "why" not "what"
- Are properly scoped and atomic
- Don't contain sensitive information (secrets, tokens, credentials)
3. Code Quality
- Run the project's tests
- Run linters/formatters if configured
- Verify build or packaging if applicable
4. Security Check
Before pushing, verify:
- ❌ No secrets in commits (.env, API keys, passwords)
- ❌ No sensitive data (credentials, tokens, private keys)
- ❌ No hardcoded passwords or tokens
- ✅
.gitignoreincludes sensitive files
Search for potential secrets:
git diff origin/main..HEAD | grep -i "password\|secret\|api_key\|token"
5. Branch Verification
Check branch state:
git status
git log origin/main..HEAD
Verify:
- On correct branch
- All changes committed
- No untracked files that should be committed
- Branch is up to date with remote base branch
6. Remote Check
Before force pushing:
git log origin/$(git branch --show-current)..HEAD
Never force push if:
- ❌ Branch is shared with others
- ❌ Branch is main/master
- ❌ Commits already pushed to remote
Only force push if:
- ✅ User explicitly requested it
- ✅ Branch is personal/feature branch
- ✅ You understand the consequences
Push Commands
Standard Push
git push
First Push (set upstream)
git push -u origin branch-name
Force Push (DANGEROUS - ask first)
# Only after explicit user permission
git push --force-with-lease
Post-Push Verification
After pushing:
- Verify CI/CD pipeline passes
- Check pull request status (if applicable)
- Verify deployment succeeded (if applicable)
- Monitor for errors in production
Common Issues
- For push rejections or diverged branches, rebase/merge per repo policy.
- If secrets were pushed, rotate credentials and remove from history.
Checklist Summary
Before git push:
- [ ] README updated (if repo has one and changes warrant it)
- [ ] Tests passing
- [ ] Linting clean
- [ ] Build successful
- [ ] No secrets in commits
- [ ] Commit messages are clear
- [ ] On correct branch
- [ ] All intended changes committed
- [ ] CI/CD will pass (reasonable expectation)
Related Skills
scruffydan/writing-skills
testing
VerifiedTrustedCommunity
Use when creating new skills, editing existing skills, or verifying skills work before deployment
SKILL.mdUpdated May 4, 2026
scruffydan/verification-before-completion
data-ai
VerifiedTrustedCommunity
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
SKILL.mdUpdated May 4, 2026
scruffydan/using-docs-fetcher
development
VerifiedTrustedCommunity
How to use @docs-fetcher to pull current, targeted external documentation (APIs, SDKs, configs, errors, version changes). Use when you need authoritative docs or examples instead of relying on memory.
SKILL.mdUpdated May 4, 2026
scruffydan/using-code-review
development
VerifiedTrustedCommunity
How and when to invoke code review agents (@code-security, @code-readability, @code-performance, @code-redundancy, @code-simplifier, @code-full-review). Use before major PRs, audits, refactors, or whenever targeted review feedback is needed.
SKILL.mdUpdated May 4, 2026