ai-team-library/claude/skills/run/SKILL.md
# Skill: Run ## Description Pulls the latest code from `main` and launches the desktop application. Designed for the workflow where development happens on a remote server and the app is run locally from freshly pulled code. ## Trigger - Invoked by the `/run` slash command. ## Usage ``` /run # Pull main and run /run main # Pull main branch and run (explicit) ``` ## Process 1. **Save current branch** — Record which branch we're on. 2. **Auto-stash if dirty** — If `git
npx skillsauth add beekeeper-lab/foundry ai-team-library/claude/skills/runInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Pulls the latest code from main and launches the desktop application. Designed for the workflow where development happens on a remote server and the app is run locally from freshly pulled code.
/run slash command./run # Pull main and run
/run main # Pull main branch and run (explicit)
git status --porcelain shows changes, run git stash --include-untracked -m "run-auto-stash". Do NOT ask — just stash.git fetch origin.git checkout main.git pull origin main.uv sync to ensure packages match the pulled code.uv run <app-name>. This runs in the foreground — the app window opens and Claude waits for it to exit.git checkout <original-branch>git stash popmain is a valid target branch. Reject anything else.uv sync before run. The pulled code may have new/changed dependencies. Always sync first.| Error | Resolution |
|-------|------------|
| Invalid branch | Report: only main is a valid target |
| Pull fails | Report error. Check network / remote state. |
| uv sync fails | Report error. May need manual dependency resolution. |
| App crashes on launch | Report the error output. Stay on the pulled branch for debugging. |
| Command blocked | Print exact command for manual execution |
development
# Skill: VDD (Verification-Driven Development) Gate ## Description Runs the programmatic VDD gate for a bean: parses the bean's `## Acceptance Criteria` section, dispatches each criterion's evidence type to the matching runner (test, lint, file, file-contains, or manual), aggregates the results into a pass/fail verdict, and writes a structured markdown report at `ai/outputs/tech-qa/vdd-<NNN>.md` (zero-padded NNN). This is the machine-checkable counterpart to the prose VDD policy in `ai/contex
tools
# Skill: Spawn Task ## Description Dispatches a single specialist persona to execute a single task with only that task's context. Auto-detects the runtime environment and chooses one of two execution paths: - **In tmux** (`$TMUX` set): spawn a worker in a git worktree using a child tmux window. Process-isolated, parallelizable, durable across the calling session's lifetime. Same pattern as `/spawn-bean` but at task granularity. - **Not in tmux**: invoke the `Agent` tool with `subagent_typ
development
# Skill: Orchestration Report ## Description Aggregates the per-bean **Orchestration Telemetry** blocks (BEAN-278) across recent Done beans and produces a markdown report that answers the architecture-aware-evaluation question: **is the orchestration paying for itself?** Distinct from `/telemetry-report` (which aggregates raw cost, duration, and tokens); this skill aggregates the orchestration-quality metrics layered on top — bounces, persona activations, contract violations, escape-hatch usag
development
# Skill: Health Check ## Description Runs all health checks defined in `ai/context/health-checks.md` and produces a table-format report. Can be called standalone or by other skills (e.g., `/long-run`). ## Trigger - Invoked by the `/health-check` slash command. - Called programmatically by `/long-run` at the start of each cycle. ## Inputs | Input | Type | Required | Description | |-------|------|----------|-------------| | health_checks | Markdown file | Yes | `ai/context/health-checks.md`