What does PASS and FAIL mean in Verify?

PASS means the specific check passed cleanly; FAIL indicates issues that require fixes and rerunning the checks.

Why are certain scripts excluded from the package validation?

Scripts/smoke-test.js is excluded by design; only scripts/statusline.js should be present in the package to enforce the intended packaging contract.

Where do path configurations come from for the no-hardcoded-path rule?

Paths must come from src/paths.js or be generated via os.tmpdir(), avoiding hardcoded ~/.claude or /tmp paths.

verify

Scanned

npx machina-cli add skill yusufalikync/ccs/verify --openclaw

Files (1)

SKILL.md

1.2 KB

Verify

Run all checks in sequence and report results.

Instructions

1. Smoke tests

npm test

All tests must pass.

2. Install cycle

node bin/cli.js install
node bin/cli.js status
node bin/cli.js uninstall
node bin/cli.js status

After install: status should show ACTIVE
After uninstall: status should show NOT INSTALLED

3. console.log check

Grep scripts/statusline.js for console.log. It must NOT contain any — only process.stdout.write() is allowed.

4. Package check

npm pack --dry-run

Verify these are included: bin/cli.js, src/, scripts/statusline.js. Verify scripts/smoke-test.js is NOT included (excluded by design — only scripts/statusline.js is in the package).

5. No hardcoded paths

Grep src/ files for hardcoded ~/.claude or /tmp/ paths. All paths should come from src/paths.js or os.tmpdir().

Output

Report each check as:

PASS: Check description
FAIL: Check description — what went wrong and how to fix

Final summary: X/5 checks passed.

Source

git clone https://github.com/yusufalikync/ccs/blob/main/.claude/skills/verify/SKILL.mdView on GitHub

Overview

Verify orchestrates a complete quality check for a project by running smoke tests, the install/uninstall cycle, console usage rules, packaging validation, and hardcoded-path audits. It reports PASS or FAIL for each check and ends with a final summary, helping teams catch regressions before release.

How This Skill Works

The tool executes checks in a defined order: smoke tests via npm test, the install/status/uninstall/status cycle with the CLI, a console.log policy check using grep on scripts/statusline.js, a packaging sanity check with npm pack --dry-run, and a hardcoded path audit across src/ files. Results are aggregated and presented as PASS/FAIL with guidance to fix failures.

When to Use It

Before publishing a release to ensure full verification
After CLI or packaging changes to validate integrity
In CI to catch packaging and path issues automatically
After install/uninstall cycles to confirm status accuracy
When auditing code for hardcoded paths and console usage

Quick Start

Step 1: Run smoke tests with npm test and confirm all tests pass
Step 2: Exercise the install cycle: install, status, uninstall, status; verify ACTIVE and NOT INSTALLED
Step 3: Run packaging and path checks: grep console usage, npm pack --dry-run with required inclusions/exclusions, and grep for hardcoded paths

Best Practices

Run verify in a clean environment to avoid stale state
Ensure npm tests pass locally before packaging
Verify the package contents include bin/cli.js, src/, and scripts/statusline.js
Avoid hardcoded paths; rely on src/paths.js or os.tmpdir()
Review each PASS/FAIL and fix issues iteratively before release

Example Use Cases

CI pipeline step that guards against regressions before a tag
Local dev validation after a major CLI refactor
Release workflow verifying packaging contents and exclusions
QA audit to ensure console.log is banned in built scripts
Security audit confirming no hardcoded temp paths

Frequently Asked Questions

Add this skill to your agents