petrogurcak/verify
plugins/development/skills/verify/SKILL.md
Runs full project verification suite (tests, build, lint/typecheck, plan task checklist, optional browser smoke test) and presents results with actual command output as evidence. Use after all plan tasks are complete, when user says "verify", "zverifikuj", or before merging to confirm everything works. NOT for running a single test file or for debugging failures (use systematic-debugging).
$ install --global
skillsauthnpx skillsauth add petrogurcak/skills verifyInstall 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:50 AM4.1s1 file scanned
SKILL.md
- name:
- verify
- description:
- Runs full project verification suite (tests, build, lint/typecheck, plan task checklist, optional browser smoke test) and presents results with actual command output as evidence. Use after all plan tasks are complete, when user says "verify", "zverifikuj", or before merging to confirm everything works. NOT for running a single test file or for debugging failures (use systematic-debugging).
- author:
- Petr
- version:
- 1.0.0
Verify
Run full verification after plan execution. Evidence before claims.
Announce: "Spoustim verifikaci."
Project State (auto-injected)
Branch: !git branch --show-current
Latest plan
!ls -t docs/plans/*.md 2>/dev/null | head -1
Git status
!git status --short
Process
-
Run project verification suite (detect stack automatically):
| Stack | Commands | | --------- | ----------------------------------------------------------------- | | Node/TS |
npm test,npx tsc --noEmit,npm run build,npm run lint| | Python |pytest,mypy .,ruff check .| | Flutter |flutter test,flutter analyze,flutter build| | PHP/Nette |vendor/bin/phpstan,vendor/bin/tester tests/| | Generic | Run whatever test/build commands exist in package.json / Makefile | -
Check plan task completion:
- Read plan file
- List each task
- Verify implementation exists (files created/modified as specified)
-
Browser smoke test (optional, for UI features):
Only if feature has web UI AND
rodneyis in PATH (check:which rodney || which ~/go/bin/rodney). Do NOT fall back to claude-in-chrome or curl — use rodney or skip:rodney start rodney open <app-url> rodney waitstable # Check key pages/elements exist rodney exists "<key-selector>" # exit 0 = OK rodney screenshot /tmp/verify-smoke.png rodney stopSkip if: no UI, no dev server, rodney not installed, pure API/CLI feature.
-
Present results with evidence:
Verifikace: - Testy: [output summary] [PASS/FAIL] - Build: exit [code] [PASS/FAIL] - Types/Lint: [output summary] [PASS/FAIL] - Plan tasks: [N/M] complete - Browser smoke: [N pages OK / skipped] [If all pass]: Vsechno OK. Chces demo (`/development:demo`), otestovat sam, nebo mergnem? [If failures]: [N] problems found. Fixing... -
If failures: Fix issues and re-run verification. Do NOT proceed.
-
If all pass: Offer three options:
/development:demo- create executable demo document (showboat)- Manual testing by user
- Proceed to
/development:merge
Rules
- Show actual command output - not "should pass" or "looks good"
- Run FULL suite - not just one test file
- Re-run after fixes - don't claim fixed without proof
- Check plan completeness - every task, not just tests passing
- Browser smoke is optional - don't fail verify just because rodney isn't installed
- Always stop rodney - never leave Chrome process running after smoke test
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