skills.rest
mDevsLabs
mDevsLabsCOMMUNITY
Explore all skills by this author →
Website𝕏@mDevsLabsGitHub

cli-backend-testing

Verify backend API changes end-to-end via the LobeHub CLI against a local dev server.

1|Updated May 20, 2026
Search Tags:#testing#integration#backend#cli#verification#trpc#dev-server
One-click install
npx skills add https://github.com/mDevsLabs/mAI --skill cli-backend-testing-mdevslabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cli-backend-testing
Source: https://github.com/mDevsLabs/mAI/tree/main/.agents/skills/cli-backend-testing
Command: npx skills add https://github.com/mDevsLabs/mAI --skill cli-backend-testing-mdevslabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Integrates CLI-driven testing with backend development to ensure API contracts and behaviors remain stable during local development.

Core Features & Use Cases

  • End-to-end verification of backend changes (TRPC routers, services, and models) via the LobeHub CLI against a local dev server.
  • Guidance for prerequisites, workflow steps, and troubleshooting to maintain testing reliability.
  • Use cases include validating API contracts, CLI outputs, and integration with frontend or server components during development.

Quick Start

Start the local dev server, authenticate the CLI, and run a representative test workflow against the API.

Frequently Asked Questions about cli-backend-testing

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

FAQPage Schema
How do I verify TRPC backend changes against a local dev server?▼

You verify TRPC backend changes by running the LobeHub CLI against a local dev server to execute end-to-end testing workflows. This validates API contracts, services, and models to ensure behaviors remain stable during local development.

What is CLI-driven backend integration testing?▼

CLI-driven backend integration testing validates API contracts and behaviors by executing CLI commands against a running local dev server. It ensures backend changes to TRPC routers and models integrate correctly without breaking frontend or server components.

Do I need a specific port for local dev server testing?▼

Yes, local dev server testing requires the dev server to be running at localhost:3011. You also need the CLI source located at lobehub/apps/cli and device-code login authentication to execute the verification workflow.

Can I use this workflow for regression testing on feature branches?▼

Yes, this workflow applies to local development, feature branches, and regression testing. It verifies TRPC routers, services, and models across these contexts to maintain API contract stability and integration reliability.

What's the best way to troubleshoot CLI backend verification failures?▼

To troubleshoot CLI backend verification failures, ensure the local dev server is running at localhost:3011 and device-code login authentication is successful. The workflow provides guidance for prerequisites and troubleshooting to maintain testing reliability.

Related Skills

Explore More Software Engineering Skills→
zmh13928433602-syszmh13928433602-sys

cli-backend-testing

Automate end-to-end backend API testing via the LobeHub CLI against a local dev server.

Community
Advanced
duwenjiduwenji

cli-backend-testing

Run LobeHub CLI end-to-end tests against a local dev server.

Community
Intermediate
EmeaAppGbbEmeaAppGbb

implementation

Generate API, Web, and Integration code slices from predefined contracts.

Official
Advanced
EdanStarfireEdanStarfire
15

backend-tester

Run isolated backend test environments on port 8001 with curl.

Community
Intermediate