← ClaudeAtlas

soleri-deliver-and-shiplisted

Triggers: "ship it", "pre-PR check", "delivery checklist", "is this ready", "final review", "ready to deploy". Pre-delivery quality gates. Use verification-before-completion for mid-workflow checks.
adrozdenko/soleri · ★ 6 · AI & Automation · score 74
Install: claude install-skill adrozdenko/soleri
# Deliver & Ship — Quality Gate Runner Run all pre-delivery quality gates before shipping. This ensures nothing leaves without passing stability checks, knowledge capture, and code quality verification. ## When to Use When work is considered "done" and ready to be committed, PR'd, or deployed. This is the last checkpoint before code leaves the developer's hands. ## Orchestration Sequence ### Step 1: Code Quality Run the project's linter, formatter, and type checker on all modified files: 1. Check for lint/format scripts in `package.json` (or equivalent) 2. Run `typecheck` / `tsc --noEmit` if TypeScript 3. Run any project-specific quality gates (clippy for Rust, mypy for Python, etc.) Any type error or lint failure is a blocker. ### Step 2: Test Suite Run the full test suite to catch regressions: ``` YOUR_AGENT_core op:admin_health ``` Verify the agent itself is healthy, then run project tests. All tests must pass. ### Step 3: Stability Assessment Classify the changes as safe or breaking: - **Safe**: Internal refactors, bug fixes, additive features (new exports, new ops) - **Breaking**: Removed exports, changed signatures, renamed public APIs, schema migrations - Breaking changes need migration guidance in the commit/PR description ### Step 4: Knowledge Audit Check if patterns discovered during this work session should be captured before shipping: ``` YOUR_AGENT_core op:memory_search params: { query: "current session" } ``` ``` YOUR_AGENT_core op:brain_sta