skills.rest
mica-agent
mica-agentOFFICIAL
Explore all skills by this author →
GitHub

verify-then-continue

Run type-checking and HTTP/UI/WebSocket verification before continuing after code changes.

Updated May 21, 2026
Search Tags:#verification#websocket#type-checking#smoke testing#backend restart#curl api#CI-like discipline
One-click install
npx skills add https://github.com/mica-agent/mica-solar-system --skill verify-then-continue
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-then-continue
Source: https://github.com/mica-agent/mica-solar-system/tree/main/.qwen/skills/verify-then-continue
Command: npx skills add https://github.com/mica-agent/mica-solar-system --skill verify-then-continue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents silently broken code by ensuring every change is actually verified before you proceed.

Core Features & Use Cases

  • Type-check enforcement: Runs npx tsc --noEmit after TypeScript edits to catch compile-time issues early.
  • Change-aware verification: Requires a backend restart after server/*.ts changes (without running restart scripts directly inside the tool’s process tree), and skips restart for project/card files that hot-reload.
  • Behavior validation: Verifies the changed surface area via HTTP endpoint curl, manual UI confirmation for card changes, and a WebSocket smoke test workflow using test/<name>-test.mjs.
  • Evidence-based reporting: Tells you to report concrete pass/fail results with actual test output and recent backend log context.

Quick Start

After editing code, run the relevant checks (type-check and endpoint/smoke validation) and report the pass/fail evidence before continuing.

Frequently Asked Questions about verify-then-continue

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

FAQPage Schema
How do I verify TypeScript backend changes before moving on?▼

Verify TypeScript backend changes by running `npx tsc --noEmit` for type-checking, restarting the `server/*.ts` process, and using curl to validate HTTP endpoints before advancing the workflow.

What does smoke testing a WebSocket endpoint involve?▼

WebSocket smoke testing involves executing a dedicated `test/<name>-test.mjs` script to validate endpoint connectivity and behavior, ensuring changed surfaces function correctly after code modifications.

Do I need to restart the backend after editing server TypeScript files?▼

Yes, backend restarts are required after modifying `server/*.ts` files to apply changes. Project and card files are exempt because they support hot-reload without a full process restart.

How do I check API endpoint behavior with curl after a code change?▼

Check API endpoint behavior with curl by making HTTP requests to the modified routes and reporting concrete pass or fail results alongside actual test output and recent backend log context.

What is the best way to prevent silent failures in TypeScript UI updates?▼

Prevent silent failures in TypeScript UI updates by enforcing type-checking with `npx tsc --noEmit` and performing manual UI confirmation for card changes to validate the updated behavior.

When should I not use a full backend restart for code verification?▼

Avoid a full backend restart when modifying project or card files because they hot-reload automatically. Restarting is only necessary for backend TypeScript files in the `server/` directory.

Related Skills

Explore More Software Engineering Skills→
lubusINlubusIN
48

frappe-project-triage

Identify Frappe project type, installed apps, version, and tooling.

Official
Intermediate
mvillmowmvillmow
18

fix-ci-failures

Diagnose CI failures by inspecting logs and reproducing issues locally.

Community
Advanced
jmaglyjmagly
175

gate-evaluation

Validate phase-gate criteria and generate pass/fail gate reports.

Community
Advanced
eng-vmessiaheng-vmessiah
2

ai-regression-testing

Automate regression tests validating API response shapes and state integrity.

Community
Intermediate