Vibeos Local Verify Deploy

Run local checks then deploy VibeOS to Timeweb.

Skill metadata

Source	Bundled (installed by default)
Path	skills/devops/vibeos-local-verify-deploy
Version	1.0.0
Author	VibeOS
License	MIT
Platforms	linux, macos
Tags	deploy, timeweb, tests, smoke, devops, no-github
Related skills	cursor-capabilities-bridge, vibeos-ops-health, requesting-code-review

Reference: full SKILL.md

info

The following is the complete skill definition that VibeOS loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.

VibeOS Local Verify + Timeweb Deploy

Local critical checks, then optional Timeweb deploy for online smoke. Does not push to GitHub. Skip deploy when the user says “только локально”.

When to Use

• After meaningful code/config/script changes in this repo
• User asks to verify, smoke-test, or deploy VibeOS
• Closing a task that normally needs online proof on VPS

Prerequisites

• Repo root with .venv or venv
• For deploy: SSH/scripts/deploy-timeweb.sh credentials (.env.timeweb locally, never committed)
• scripts/run_tests.sh, scripts/run_critical.sh, scripts/deploy-timeweb.sh

How to Run

From repo root:

source .venv/bin/activate  # or venv
scripts/run_tests.sh <touched-tests> -q
# if core/invariants touched:
scripts/run_critical.sh
# if online validation needed:
TIMEWEB_RUN_STRESS=0 ./scripts/deploy-timeweb.sh

Quick Reference

Goal	Command
One test file	scripts/run_tests.sh tests/path/test_x.py -q
Release subset	scripts/run_critical.sh
Kanban stress	scripts/run_stress.sh (not via run_tests.sh)
Deploy + post-upload	./scripts/deploy-timeweb.sh
Deploy without stress	TIMEWEB_RUN_STRESS=0 ./scripts/deploy-timeweb.sh

Procedure

1. Identify touched areas; run the smallest relevant scripts/run_tests.sh paths.
2. If toolsets/plugins/hooks/invariants changed, also run scripts/run_critical.sh.
3. If the change must be proven on VPS and user did not forbid deploy, run scripts/deploy-timeweb.sh.
4. Report: what ran locally, whether Timeweb deploy ran, smoke result.
5. Do not git push, gh pr create, or trigger GitHub Actions.

Pitfalls

• scripts/run_tests.sh tests/stress/ collects zero tests — use run_stress.sh.
• Never rsync .env / .env.timeweb / keys.
• “Deploy” here means Timeweb, not GitHub.
• Docs-only or explicit “без деплоя” → stop after local checks.

Verification

• Local command exit code 0
• After deploy: post-upload script finished; note remote path (~/vibeos-staging by default) and any health/smoke output