skills.rest
Adelie-Squad
Adelie-SquadOFFICIAL
Explore all skills by this author →
GitHub

build-test

Run npx tsc --noEmit and npm run build, then verify dist/bin/solo-agents.js exists.

17|1|Updated Feb 3, 2026
Search Tags:#typescript#npm#verification#build#ci#smoke-test#dist
One-click install
npx skills add https://github.com/Adelie-Squad/solopreneur-team-agents --skill build-test
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: build-test
Source: https://github.com/Adelie-Squad/solopreneur-team-agents/tree/main/.claude/skills/build-test
Command: npx skills add https://github.com/Adelie-Squad/solopreneur-team-agents --skill build-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill makes it easy to confirm the TypeScript project compiles and its smoke test artifacts are ready before releasing or shipping new CLI updates.

Core Features & Use Cases

  • Type checking: Run npx tsc --noEmit to ensure the source tree satisfies all TypeScript constraints without producing extra files.
  • Build and verification: Follow the npm run build step and check that dist/bin/solo-agents.js exists to confirm the CLI bundle was generated.
  • Use case: Before tagging a release, run this workflow to prove the build pipeline succeeds across local dev and CI agents.

Quick Start

Run the build-test workflow by executing npx tsc --noEmit, npm run build, and verifying that dist/bin/solo-agents.js exists.

Frequently Asked Questions about build-test

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

FAQPage Schema
How do I validate a TypeScript build and smoke test before a release?▼

To validate a TypeScript build and smoke test, run npx tsc --noEmit for type checking, execute npm run build to generate artifacts, and verify that dist/bin/solo-agents.js exists to confirm the CLI bundle was successfully generated.

What does npx tsc --noEmit do in a TypeScript build pipeline?▼

The npx tsc --noEmit command performs type checking to ensure the source tree satisfies all TypeScript constraints without producing extra output files, serving as a pre-build validation step before running npm run build.

How can I verify my npm build generated the correct dist artifacts?▼

You can verify npm build artifacts by checking that the expected output files, specifically dist/bin/solo-agents.js, exist in the distribution folder after the build process completes successfully.

Does this build verification workflow work for CI validation scenarios?▼

Yes, this build verification workflow targets CI validation scenarios, ensuring the TypeScript project compiles and smoke test artifacts are ready across local development and CI agents before shipping new CLI updates.

Why do I need to run tsc --noEmit before npm run build?▼

Running tsc --noEmit before npm run build isolates TypeScript type checking from the bundling step, ensuring source constraints are validated without generating extra files before the actual build produces the dist artifacts.

Related Skills

Explore More Software Engineering Skills→
luyi985luyi985

compiler-performance

Optimize TypeScript compilation with project references and incremental builds.

Community
Intermediate
PionpillPionpill
12

package-publish

Publish retikz npm packages with synchronized versions, changelogs, and validated release workflows.

Community
Advanced
devkit-stackdevkit-stack

github-actions-templates

Provide GitHub Actions YAML templates for CI/CD pipelines with Docker builds and Kubernetes deployments.

Official
Basic
parhummparhumm
25

dev-verify

Automate install, type-check, build, and health checks across multi-stack environments.

Community
Intermediate