petrogurcak/merge
plugins/development/skills/merge/SKILL.md
Commits current work, merges feature branch into development, re-runs tests on merged result, and cleans up the feature branch and worktree. Use after verification passes, when user says "merge", "mergni", or when the verify skill confirms all checks pass. NOT for merging to main/production or for creating pull requests.
$ install --global
skillsauthnpx skillsauth add petrogurcak/skills mergeInstall 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, 4:49 AM4.6s1 file scanned
SKILL.md
- name:
- merge
- description:
- Commits current work, merges feature branch into development, re-runs tests on merged result, and cleans up the feature branch and worktree. Use after verification passes, when user says "merge", "mergni", or when the verify skill confirms all checks pass. NOT for merging to main/production or for creating pull requests.
- author:
- Petr
- version:
- 1.0.0
Merge
Commit, merge to development, verify, cleanup.
Announce: "Merguji do development."
Process
-
Commit current work (if uncommitted changes exist):
git add [relevant files] git commit -m "feat: [description]" -
Switch to development and merge:
git checkout development git pull git merge <feature-branch> -
Verify on development:
- Run test suite again on merged result
- Run build
- Show evidence of success
-
Cleanup:
- Delete feature branch:
git branch -d <feature-branch> - Remove worktree if used:
git worktree remove <path>
- Delete feature branch:
-
Report:
Merge hotovy: - Branch: <feature-branch> merged do development - Testy na development: PASS - Branch smazan: yes - Worktree: [removed / n/a] Hotovo. Spoustim wrap-up.
Error Handling
- Merge conflicts: Show conflicts, help resolve, re-run tests after resolution
- Test failures on development: Fix on development, re-run tests, don't leave development broken
- No development branch: Ask user which branch to merge to
Rules
- Always verify after merge - merged code can break even if both branches were green
- Always delete feature branch after successful merge (unless user says otherwise)
- Never force-push to development
Related Skills
petrogurcak/testimonial-harvesting
development
VerifiedTrustedCommunity
Builds a pre-launch social proof strategy through structured beta programs using D'Souza Brain Audit interviews. Use when launching new products/services and need compelling testimonials, planning a beta cohort, designing interview questions to harvest objection-busting social proof, improving video testimonials for landing pages, or designing case studies with metrics. Trigger phrases include "beta tester program for testimonials", "pre-launch social proof", "Brain Audit testimonial framework", "case study harvest", "reverse testimonial", "video testimonial mechanics", "social proof landing page", "sběr referencí", "beta tester program", "testimonial pro landing page", "social proof před launchem", "rozhovor s klientem", "case study sběr", "reference před spuštěním". NOT for ongoing case study production (use growth-hacking case-study approach), offer design (use offer-creation), or conversion optimization (use ux-optimization).
2SKILL.mdUpdated May 14, 2026
petrogurcak/launch-orchestrator
development
VerifiedTrustedCommunity
Use when planning a product launch and the product type is unclear or could be either generic (SaaS/app/physical) or info-product. Routes between marketing:launch-strategy (generic launches) and marketing:info-product-launch (courses, memberships, ebooks, cohorts, communities). Trigger phrases - "launch", "spuštění", "go-to-market", "product launch", "release strategy", "uvedení na trh", "launch plan", "spuštění produktu", "launch sequence", "launch strategy". Do NOT trigger when product type is already clear (use specific skill directly).
2SKILL.mdUpdated May 14, 2026
petrogurcak/info-product-launch
testing
VerifiedTrustedCommunity
Specialized 8-week launch cadence for info-products — online courses, cohort programs, memberships, communities, ebooks, masterminds. Combines Jeff Walker's Product Launch Formula (Seed/Internal/JV variants, PLC sequence, open-cart day-by-day) with Stu McLaren's membership mechanics (closed cart, Success Path) and Hormozi Grand Slam Offer stacking. Use when planning "launch online kurzu", "info-product launch", "PLF launch", "course launch", "membership launch", "cohort launch", "ebook launch", "open cart close cart", "8-week launch of online course", "beta cohort to launch sequence", "spuštění kurzu", "launch členské sekce", "open cart strategie". Differentiates from marketing:launch-strategy (generic SaaS/app launches) — info-product-specific. NOT for SaaS launches, physical products, or services.
2SKILL.mdUpdated May 14, 2026
petrogurcak/mobile-store-release
development
VerifiedTrustedCommunity
Use when releasing an Expo/React Native mobile app to App Store and Google Play - covers eas submit, ASC "Submit for Review", Play promote Internal→Production, OTA update, and decoding common silent failures (Apple agreement expiry, missing English locale, Background Location declaration, web bundle failure on react-native-maps).
2SKILL.mdUpdated May 14, 2026