| name | deploy-check |
| description | This skill should be used when the user asks to 'check if ready to deploy', 'pre-deploy check', 'verify before deploying', 'deployment readiness', 'is it ready to ship', or wants pre-deployment verification. |
| disable-model-invocation | true |
| allowed-tools | Read, Write, Edit, Bash, Grep, Glob |
| model | inherit |
| argument-hint | |
Deploy Check
Run a full pre-deployment verification pipeline: lint, test, build. Fix any failures automatically.
What to do
- Run the full pipeline (lint + test + build).
- If anything fails, read the error output, fix the issue, and re-run.
- Repeat until all three pass.
Flow
flow:
retry max 5
run: npm run lint && npm test && npm run build
if command_failed
prompt: The pipeline failed. Read the error output, fix the issue, and try again.
end
end
done when:
tests_pass
lint_pass
Rules
- Fix the first error you encounter — later stages may depend on earlier ones.
- If a fix in a later stage breaks an earlier stage, the next retry will catch it.
- Report the final status of all three stages when done.
Environment-Specific Command Mapping
When the repo uses a non-Node stack, substitute equivalent commands:
- Python:
ruff check . && pytest && python -m build
- Go:
go test ./... && go vet ./...
- Rust:
cargo test && cargo clippy -- -D warnings && cargo build
Use project-native commands if scripts are already defined in package/tooling config.
Deployment Readiness Checklist
Before declaring ready:
- Lint is clean.
- Tests are green.
- Build/package step completes.
- No unresolved TODO-level warnings introduced in touched files.
- Any migration or rollout prerequisites are called out explicitly.
Failure Classification
lint failures: style/static correctness; fix first.test failures: behavior regressions; isolate smallest failing unit first.build failures: integration/packaging/runtime typing.
If failures are flaky or environment-specific, report the exact command and stderr fragment.
Done Response Template
Lint: pass/failTests: pass/failBuild: pass/failReady: yes/noNotes: any remaining risk or prerequisite
