Menu
Run the full pre-release verification gate (lint, types, tests, coverage) and report readiness
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
ChatbotX is an open-source chat marketing platform for managing contacts, conversations, flows, broadcasts, and sequences across WhatsApp, Messenger, Instagram, TikTok, Telegram, Zalo OA, Email, and Webchat. An alternative to ManyChat, Chatfuel, Wati, Respond, etc...
Create and modify integration channels (messenger, whatsapp, zalo, tiktok, webchat, etc.) for the chatbot platform. Use when adding a new channel integration, modifying webhook handlers, working with message send/receive, or connecting external platforms.
ChatbotX is an open-source chat marketing platform for managing contacts, conversations, flows, broadcasts, and sequences across WhatsApp, Messenger, Instagram, TikTok, Telegram, Zalo OA, Email, and Webchat. An alternative to ManyChat, Chatfuel, Wati, Respond, etc...
Work with the ChatbotX contact filter system — the shared filter model behind the contacts list, conversations, and broadcast audiences. Use when adding a filter field or operator, changing the filter UI, editing the SQL query builder, or enforcing an audience constraint. Covers the definitions single-source, the two operator-rule sources that must stay in sync, NULL / negation three-valued logic, relation EXISTS subqueries, and the excludeFields mechanism.
Use before committing changes to auth, workspace scoping, channel webhooks, AI tools/MCP, permission settings, or anything handling untrusted channel content in ChatbotX. A repo-specific security checklist covering tenant isolation, prompt injection via channel content, the Bash permission allowlist, and secret handling. Read before security-sensitive work; pair with the global security-reviewer agent for deep dives.
Implement approved technical plans with execution-first behavior
| name | source-command-release-check |
| description | Run the full pre-release verification gate (lint, types, tests, coverage) and report readiness |
Use this skill when the user asks to run the migrated source command release-check.
Verify the repo is release-ready by running the gate sequence from the testing-workflow skill. CI only builds Docker images, so this gate is your real safety net — run it before tagging a release or opening a release PR.
Scope — determine what changed: git diff main...HEAD --stat (or the given range). Identify the touched workspaces.
Lint — pnpm lint. If it fails, stop and report; suggest pnpm fix for auto-fixable issues.
Types — for each touched workspace: pnpm --filter <workspace> check-types. Report the first failure per workspace.
Tests + coverage — run the affected packages' Vitest suites. Do not set VITEST_SKIP_COVERAGE_THRESHOLDS; the 80% threshold must hold (packages/vitest-config/src/node.ts). Report any suite below threshold.
Invariant scan — dispatch the invariant-guard agent on the diff to catch the non-lintable invariants.
Secret scan — grep the diff for credential patterns (PGPASSWORD, DATABASE_URL=, API keys); confirm no .env/secret is staged.
A readiness checklist:
RELEASE CHECK
- lint: PASS / FAIL (<detail>)
- types: PASS / FAIL (<workspace>)
- tests: PASS / FAIL (<suite>)
- coverage: >=80% / BELOW (<package> <n>%)
- invariants: PASS / <n> violations
- secrets: CLEAN / FOUND (<file:line>)
=> READY / NOT READY