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

testing-workflow

Verifies ChatbotX changes with linting, type checks, tests, and 80% coverage.

601|129|Updated Dec 9, 2024
Search Tags:#typescript#vitest#testing#linting#quality gate#coverage#chatbotx
One-click install
npx skills add https://github.com/ChatbotXIO/ChatbotX --skill testing-workflow-chatbotxio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing-workflow
Source: https://github.com/ChatbotXIO/ChatbotX/tree/main/.agents/skills/testing-workflow
Command: npx skills add https://github.com/ChatbotXIO/ChatbotX --skill testing-workflow-chatbotxio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents ChatbotX changes from being called done before they have passed the real local verification gate. It reduces regressions by making linting, type checks, tests, and coverage part of the normal delivery flow.

Core Features & Use Cases

  • Verification sequence: Runs the expected gate in order so failures are caught early and fixed before moving on.
  • Test placement guidance: Explains where to put app, package, integration, and colocated unit tests in this repository.
  • Coverage discipline: Reinforces the 80 percent threshold and warns against bypassing thresholds when coverage is weak.
  • Use case: Before merging a change to a route, worker, repository, or channel integration, use this Skill to confirm the correct checks and test scope.

Quick Start

Use this Skill to verify the touched ChatbotX workspace by following the lint, type check, test, and coverage gate in order and reporting any failures honestly.

Frequently Asked Questions about testing-workflow

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

FAQPage Schema
How do I run a local quality gate for TypeScript changes before merging?▼

Coverage discipline requires maintaining an 80 percent threshold without bypassing or skipping thresholds when coverage is weak. This prevents merging untested code and reduces regressions by enforcing strict coverage metrics.

Where should I place tests for app, package, and channel integration workspaces?▼

The verification sequence runs linting first, followed by workspace type checks, then targeted Vitest execution. This ordered gate catches failures early so issues are fixed before moving to the next stage of the delivery flow.

Can I skip the coverage threshold when test coverage is weak for a new route?▼

Use this verification gate before merging changes to routes, worker handlers, repositories, or channel integrations across app and package workspaces. It confirms correct checks and test scope are met before delivery.

What does the Vitest quality gate check during a ChatbotX workflow?▼

The verification gate applies to new or modified tests, routes, actions, repositories, worker handlers, and channel integrations across both app and package workspaces within the ChatbotX repository.

Related Skills

Explore More Software Engineering Skills→
devrelaicomdevrelaicom
37

midnight-cq:quality-check

Run and interpret linting, type checking, contract compilation, and test failures for Midnight projects.

Official
Advanced
adryanmoldokkr32-pixeladryanmoldokkr32-pixel

land-and-deploy

Merge pull requests, monitor CI, deploy to production, and verify health with canary checks.

Community
Intermediate
hivellmhivellm
15

rulebook-typescript

Automates TypeScript project setup with strict mode, Vitest, ESLint, and CI/CD templates.

Official
Intermediate
DarkMonkDevDarkMonkDev
1

test-environment

Run unit, integration, and end-to-end tests in isolated containers.

Community
Advanced