Agent skill

ship

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'.

Stars 115
Forks 18

Install this agent skill to your Project

npx add-skill https://github.com/alfredolopez80/multi-agent-ralph-loop/tree/main/.claude/skills/ship

SKILL.md

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

bash
/ship                    # Run full checklist
/ship --skip-browser     # Skip browser tests (backend-only)

Behavior

  1. Run each check sequentially
  2. BLOCKING checks (1-2): must pass to ship
  3. ADVISORY checks (3-8): reported but don't block
  4. 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.

Expand your agent's capabilities with these related and highly-rated skills.

alfredolopez80/multi-agent-ralph-loop

browser-test

Browser testing using Chrome DevTools MCP and Playwright for visual verification. Start dev server, navigate, screenshot, Lighthouse audit, console errors, network check. Use when: (1) verifying frontend changes, (2) accessibility auditing, (3) performance testing, (4) visual regression. Triggers: /browser-test, 'test in browser', 'visual test', 'lighthouse audit'.

115 18
Explore
alfredolopez80/multi-agent-ralph-loop

crafting-effective-readmes

Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.

115 18
Explore
alfredolopez80/multi-agent-ralph-loop

stop-slop

A skill for removing AI-generated writing patterns ('slop') from prose. Eliminates telltale signs of AI writing like filler phrases, excessive hedging, overly formal language, and mechanical sentence structures. Use when: writing content that should sound human and natural, editing AI-generated drafts, cleaning up prose for publication, or any content that needs to sound authentic rather than AI-generated. Triggers: 'stop-slop', 'remove AI tells', 'clean up prose', 'make it sound human', 'edit AI writing'.

115 18
Explore
alfredolopez80/multi-agent-ralph-loop

bugs

Bug hunting with Codex CLI Use when: (1) /bugs is invoked, (2) task relates to bugs functionality.

115 18
Explore
alfredolopez80/multi-agent-ralph-loop

adversarial

Multi-Agent Adversarial Analysis System for code security

115 18
Explore
alfredolopez80/multi-agent-ralph-loop

senior-software-engineer

Global skill enforcing senior software engineering best practices

115 18
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results