n-start-check

Automate smoke-testing of start scripts across Bun monorepo workspaces.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/vitaliytv/7n --skill n-start-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n-start-check
Source: https://github.com/vitaliytv/7n/tree/main/.cursor/skills/n-start-check
Command: npx skills add https://github.com/vitaliytv/7n --skill n-start-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the verification of workspace startup in a Bun monorepo, identifying immediate crashes or configuration issues before they impact development.

Core Features & Use Cases

  • Automated Workspace Scanning: Automatically detects all workspaces and their respective start scripts.
  • Isolated Smoke Testing: Executes start scripts sequentially to verify service readiness and catch initialization errors.
  • Side-Effect Management: Safely identifies and reverts file system changes caused by test runs to maintain repository integrity.

Quick Start

Run the n-start-check skill from the root of your repository to verify that all workspaces start correctly without errors.

Frequently Asked Questions about n-start-check

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

FAQPage Schema
How do I run smoke tests for start scripts across workspaces in a Bun monorepo?

To run smoke tests in a Bun monorepo, you execute the skill from the repository root. It automatically scans workspaces and sequentially executes start scripts to identify initialization failures and configuration errors.

What is automated smoke testing for Bun monorepos?

Automated smoke testing for Bun monorepos is the process of sequentially executing workspace start scripts to verify service readiness. It identifies immediate crashes, missing dependencies, and configuration issues before they impact development.

Do I need a specific CLI to automate workspace scanning in a Bun monorepo?

Yes, you need the @nitra/cursor CLI to automate workspace scanning in a Bun monorepo. The CLI is required to manage process execution, workspace detection, and state restoration during smoke testing.

Can smoke testing start scripts revert file system changes in a Bun monorepo?

Yes, smoke testing start scripts can safely revert file system changes in a Bun monorepo. The skill manages side-effects by identifying and restoring any file modifications caused by test runs to maintain repository integrity.

What is the best way to catch initialization failures in a Bun monorepo?

The best way to catch initialization failures in a Bun monorepo is using automated smoke testing. It sequentially verifies each workspace's start script to immediately detect service crashes and missing dependencies.

Why does my workspace startup fail during automated Bun monorepo checks?

Workspace startup fails during automated Bun monorepo checks due to initialization failures, missing dependencies, or configuration errors. The smoke test isolates these issues by executing start scripts sequentially across detected workspaces.