dashclaw-ship
SolidThe single command that gets a DashClaw change ON MAIN AND LIVE — it resolves everything blocking production, never defers, and never hands back a checklist. Lands feature branches on main (rebase, gate, merge, push so Vercel deploys), bumps the unified platform+SDK version, and realigns every *description* of the system with the live code: README, PROJECT_DETAILS, SDK READMEs, /docs, generated artifacts (API inventory, OpenAPI, livingcode, the platform skill), plugins/skills/hooks/MCP, marketing/landing pages, the drift-prone hardcoded counts (routes, SDK methods, MCP tools/resources, guard policies) and stale freshness date-stamps. The one step it can't finish itself is the credential-gated SDK publish (`npm run release:sdks`). Use whenever the user wants to ship, land, or finish a change — get it on main, make it live, cut a release, bump the version, refresh all the docs, make everything accurate, fix wrong counts or old dates. Not for building or debugging the feature itself.
Install
Quality Score: 89/100
Skill Content
Details
- Author
- ucsandman
- Repository
- ucsandman/DashClaw
- Created
- 5 months ago
- Last Updated
- today
- Language
- TypeScript
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
ship-feature
Drives a one-line feature brief to a green, review-clean PR — autonomously — in whatever project the current directory belongs to: question-first intake, durable spec, implement, local gates (simplify, optional codex CLI review, build/lint/test vs baseline, adversarial review, a REAL user-perspective end-to-end verification), open the PR READY, loop the configured review bots to zero unresolved threads at the head SHA, hand back for ONLY the merge decision (or merge through the fail-closed gate script under an explicit in-chat grant), then validate the release. First run in a new project onboards itself: detects the stack, interviews the user, writes a profile. Use whenever the user asks to build, add, implement, wire up, or ship a feature or non-trivial behavior change in this project, end to end. Do NOT trigger for a single typo or copy tweak, read-only questions or research, reviewing an already-open PR, or promoting a merged change to production.
ship-ready
Turn any unit of work — a freeform feature request OR a Jira/Linear/GitHub issue — into ship-ready, reviewed, tested code with no bugs and no tech debt. Grill requirements to zero ambiguity and detect the project (stack/commands/conventions) at intake, then run one autonomous Workflow: plan, research, implement, converge on correctness+completeness behind a machine gate, take ONE advisory maintainability pass, and emit a structured ship verdict. Project-agnostic — backend, frontend, full-stack, mobile (incl. Flutter), CLI, library, or infra; monolith or microservices; one repo or a feature spanning several. Invoke it to build, implement, ship, deliver, or finish a feature, or to work a ticket/issue end to end (e.g. "build the X feature", "work ABC-123", "take this to a merge-ready PR") — for a whole unit of work, not a one-line edit, a review, or a pure question.
ship
Push a committed feature branch, open a PR, watch CI, and (only on explicit confirmation) squash-merge and clean up. Use when the user says "ship this", "push and open a PR", "is CI green yet", or asks to merge a PR that's already open. Assumes the branch is already committed — this skill does not stage or commit anything. Does not require ending at a merge: an open, CI-green PR is a valid stopping point.