validate-canvas-change

Validate Canvas Workspace changes with configurable quick, standard, and release checks.

27|1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/hua-bang/pulse-agent --skill validate-canvas-change
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-canvas-change
Source: https://github.com/hua-bang/pulse-agent/tree/main/apps/canvas-workspace/harness/skills/validate-canvas-change
Command: npx skills add https://github.com/hua-bang/pulse-agent --skill validate-canvas-change

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the need for targeted validation of changes made to the Canvas Workspace, ensuring code quality and performance before release.

Core Features & Use Cases

  • Selective Validation: Offers different levels of validation (quick, standard, release) to suit various stages of development and release readiness.
  • Performance Focus: Identifies performance-sensitive changes and provides a focused performance report.
  • Use Case: When making changes to the Canvas Workspace, use this Skill to run a quick validation during development or a full performance report for a release candidate.

Quick Start

Run the validate-canvas-change skill with the desired level of validation, e.g., pnpm run harness -- --level standard.

Frequently Asked Questions about validate-canvas-change

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

FAQPage Schema
How do I validate Canvas Workspace changes before a release?

To validate Canvas Workspace changes before a release, run the validation harness with a release-level check to thoroughly assess code quality and performance readiness. This identifies performance-sensitive changes and provides a focused performance report for release candidates.

What levels of validation are available for checking Canvas Workspace code quality?

Canvas Workspace code quality validation supports three configurable levels of thoroughness: quick, standard, and release. These levels suit various stages of iterative development and release preparation by providing targeted validation checks based on your current needs.

When should I use release-level validation versus a quick check for Canvas Workspace updates?

Use quick validation during active iterative development for fast feedback, and switch to release-level validation when preparing a release candidate. Release-level checks provide a full performance report to ensure performance-sensitive changes meet critical code quality standards.

How do I run a standard validation check on my Canvas Workspace changes?

Run a standard validation check on Canvas Workspace changes by executing the validation harness with the standard level parameter, such as `pnpm run harness -- --level standard`. This provides balanced thoroughness for ongoing iterative development.

Does Canvas Workspace validation require any external dependencies?

Canvas Workspace validation operates without external dependencies, using included scripts to assess code quality and performance. It is designed for environments where performance and code quality are critical, ensuring release readiness without requiring additional setup.

What is the best way to identify performance-sensitive changes in a Canvas Workspace?

The best way to identify performance-sensitive changes in a Canvas Workspace is to run the validation skill with a release-level check. This generates a focused performance report that highlights critical issues affecting code quality and release readiness.