alfredolopez80/ship
.claude/skills/ship/SKILL.md
Pre-launch shipping checklist orchestrating /gates, /security, /browser-test, /perf. Ensures nothing ships without passing all quality checks. Use when: (1) before deploying, (2) before merging to main, (3) before release. Triggers: /ship, 'ship it', 'ready to deploy', 'pre-launch check'.
$ install --global
skillsauthnpx skillsauth add alfredolopez80/multi-agent-ralph-loop shipInstall 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 15, 2026, 6:07 PM7.8s1 file scanned
SKILL.md
- # VERSION:
- 3.0.0
- name:
- ship
- description:
- Pre-launch shipping checklist orchestrating /gates, /security, /browser-test, /perf. Ensures nothing ships without passing all quality checks. Use when: (1) before deploying, (2) before merging to main, (3) before release. Triggers: /ship, 'ship it', 'ready to deploy', 'pre-launch check'.
- argument-hint:
- [--skip-browser]
- user-invocable:
- true
Ship — Pre-Launch Checklist v3.0
Orchestrate all quality checks before shipping.
Checklist
SHIP CHECKLIST
==============
[ ] 1. /gates — All 4 stages pass (correctness, quality, security, consistency)
[ ] 2. /security — No critical/high vulnerabilities
[ ] 3. /browser-test — No console errors, Lighthouse > 90 (if frontend)
[ ] 4. /perf audit — Core Web Vitals in target range (if frontend)
[ ] 5. Git status — No uncommitted changes
[ ] 6. Tests — All tests pass
[ ] 7. ADR — Major decisions documented (if complexity >= 7)
[ ] 8. Spec — Exit criteria met (if spec exists)
Usage
/ship # Run full checklist
/ship --skip-browser # Skip browser tests (backend-only)
Behavior
- Run each check sequentially
- BLOCKING checks (1-2): must pass to ship
- ADVISORY checks (3-8): reported but don't block
- Output: summary with PASS/FAIL per check
Anti-Rationalization
| Excuse | Rebuttal | |---|---| | "It's just a small change" | Small changes cause big outages. Run the checklist. | | "I already tested manually" | Manual testing misses what automated checks catch. | | "The deadline is tight" | Shipping broken code costs more time than the checklist. |
Related Skills
alfredolopez80/vault
development
VerifiedTrustedCommunity
Living knowledge base management. Actions: search (query vault), save (store learning), index (update indices), compile (raw->wiki->rules graduation), init (create vault structure). Follows Karpathy pipeline: ingest->compile->query. Use when: (1) searching accumulated knowledge, (2) saving learnings, (3) compiling raw notes into wiki, (4) initializing a new vault. Triggers: /vault, 'vault search', 'knowledge base', 'save learning'.
121SKILL.mdUpdated Apr 15, 2026
alfredolopez80/spec
testing
VerifiedTrustedCommunity
Produce a verifiable technical specification before coding. 6 mandatory sections: Interfaces, Behaviors, Invariants (from Aristotle Phase 2), File Plan, Test Plan, Exit Criteria (executable bash commands + expected results). Use when: (1) before implementing features with complexity > 4, (2) as Step 1.5 in orchestrator workflow, (3) when requirements need formalization. Triggers: /spec, 'create spec', 'write specification', 'technical spec'.
121SKILL.mdUpdated Apr 15, 2026
alfredolopez80/perf
development
VerifiedTrustedCommunity
Performance optimization skill. Core Web Vitals via Lighthouse, bundle size analysis, metrics tracking over time. Use when: (1) optimizing frontend performance, (2) analyzing bundle size, (3) tracking metrics regression. Triggers: /perf, 'performance audit', 'core web vitals', 'bundle size'.
121SKILL.mdUpdated Apr 15, 2026
alfredolopez80/exit-review
development
VerifiedTrustedCommunity
End-of-session learning classification. Reviews accumulated learnings and classifies each as GREEN (generic, goes to global wiki), YELLOW (project-specific, goes to project wiki), or RED (sensitive, discarded). Triggered at session end via Stop hook. Use when: (1) session ending, (2) manual review of learnings. Triggers: /exit-review, 'review learnings', 'classify learnings'.
121SKILL.mdUpdated Apr 15, 2026