build-dashclaw
FeaturedContribute to the DashClaw codebase — architecture, scaffolding, tests, CI
Install
Quality Score: 92/100
Skill Content
Details
- Author
- ucsandman
- Repository
- ucsandman/DashClaw
- Created
- 6 months ago
- Last Updated
- 3 days ago
- Language
- TypeScript
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
setup-dashclaw
Set up a DashClaw instance, install the CLI tool, and configure Claude Code hooks
instrument-agent
Integrate DashClaw SDK into any agent using the 4-step governance loop
dashclaw-ship
The 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, download bundles), 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.