starwards-verification

Run Starwards verification commands and report completion with evidence.

42|2|Updated Mar 17, 2019
One-click install
npx skills add https://github.com/starwards/starwards --skill starwards-verification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: starwards-verification
Source: https://github.com/starwards/starwards/tree/main/.claude/skills/starwards-verification
Command: npx skills add https://github.com/starwards/starwards --skill starwards-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires npm.

What problem does it solve?

Prematurely claiming "done" without thorough verification leads to regressions, broken builds, and wasted time. This skill enforces an evidence-based verification process for Starwards, ensuring all code changes are fully tested and validated before completion.

Core Features & Use Cases

  • Comprehensive Test Suite: Guides through running unit, integration, E2E, type, and formatting checks across all modules.
  • Evidence-Based Claims: Mandates running actual commands and presenting their output as proof of completion, eliminating assumptions.
  • Use Case: Before committing any changes or creating a pull request, activate this skill to run a full verification sequence, guaranteeing your work is stable and meets quality standards.

Quick Start

"I've finished implementing a feature. How do I verify it's ready to commit?"

Frequently Asked Questions about starwards-verification

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

FAQPage Schema
How do I verify my code changes are ready to commit?

Code verification runs unit tests, integration tests, E2E tests, type checking, and builds to confirm all changes work correctly. Execute npm test, npm run test:e2e, npm run test:types, and npm run build, then review the output and exit codes to ensure everything passes before committing.

What testing does code verification cover?

Verification covers unit tests, integration tests, end-to-end tests, type checking, and build validation. Running the full sequence—npm test, npm run test:e2e, npm run test:types, and npm run build—ensures your code meets quality standards across all test layers.

Why should I verify code before creating a pull request?

Verification prevents regressions, broken builds, and wasted review cycles by requiring evidence that all tests pass and the build succeeds. Running the complete verification sequence guarantees your changes are stable and meet quality standards before submission.

Can I use verification across different project modules?

Yes, verification applies to Starwards-powered projects across core, server, browser, and node-red modules. The same npm-based verification commands work consistently, ensuring comprehensive quality assurance regardless of module type.

What output does verification provide?

Verification collects full command outputs and exit codes from all test and build runs, then reports the final status with supporting artifacts. This evidence-based approach eliminates assumptions and clearly documents what passed or failed.