skills.rest
ChatbotXIO
ChatbotXIOOFFICIAL
Explore all skills by this author →
Website𝕏@phong_makerGitHub

source-command-release-check

Runs lint, type, test, coverage, invariant, and secret checks to verify release readiness.

722|195|Updated Dec 9, 2024
Search Tags:#type checking#Vitest#coverage#lint#Monorepo#ci#release check
One-click install
npx skills add https://github.com/ChatbotXIO/ChatbotX --skill source-command-release-check
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-command-release-check
Source: https://github.com/ChatbotXIO/ChatbotX/tree/main/.agents/skills/source-command-release-check
Command: npx skills add https://github.com/ChatbotXIO/ChatbotX --skill source-command-release-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before tagging a release or opening a release PR, teams need confidence that the codebase passes all quality gates, especially when CI only builds Docker images and does not run tests. This Skill runs the full pre-release verification sequence and reports a clear readiness checklist.

Core Features & Use Cases

  • Full Gate Sequence: Runs lint, per-workspace type checks, Vitest suites with enforced 80% coverage thresholds, an invariant scan on the diff, and a secret scan for credentials.
  • Scoped Verification: Determines what changed via git diff and only type-checks and tests the touched workspaces.
  • Structured Readiness Report: Outputs a PASS/FAIL checklist ending in a READY or NOT READY verdict.
  • Use Case: Before tagging v2.1.0, run the release check to confirm lint passes, all touched workspaces type-check, coverage stays at or above 80%, no invariant violations exist, and no secrets are staged.

Quick Start

Run the release check on my current branch against main and tell me if it is ready to tag.

Frequently Asked Questions about source-command-release-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a monorepo is ready for release?▼

Run the release-check gate sequence: lint the repo, type-check each touched workspace, run affected Vitest suites with coverage thresholds, scan the diff for invariants and secrets. The result is a READY or NOT READY checklist.

How to run type checks only on changed pnpm workspaces?▼

Use git diff to identify touched workspaces, then run pnpm --filter <workspace> check-types for each one. This scopes verification to changed code instead of checking the entire monorepo.

Does this release check enforce test coverage thresholds?▼

Yes, the 80% coverage threshold defined in the shared Vitest config must hold. The check never sets VITEST_SKIP_COVERAGE_THRESHOLDS, and any suite below threshold is reported as a failure.

Can the release check fix failing lint or type errors automatically?▼

No, it is read-only verification. It reports failures and may suggest pnpm fix for auto-fixable lint issues, but it never edits code to make a gate pass.

Why run a release check if CI already builds Docker images?▼

CI in this repo only builds Docker images and does not run lint, types, or tests. The release check is the actual safety net that catches quality regressions before tagging a release.

Related Skills

Explore More Software Engineering Skills→
LiozShorLiozShor
2

git-ship

Validate Git branches, diffs, and commit messages before pushing or merging.

Community
Advanced
orient-botorient-bot

release-version

Create Orient releases with versioning, changelog updates, and Docker image tags.

Official
Intermediate
dollspace-gaydollspace-gay
6

review-pre-commit

Scan working code diffs for stubs, debug leftovers, and crosslink documentation.

Community
Intermediate
nullhacknullhack

code-quality

Run ruff, pyright, and pytest coverage checks for Python projects.

Community
Intermediate