mirror of
https://github.com/openprose/prose.git
synced 2026-09-19 05:55:05 +08:00
dan
624e75ad89
* Refresh OpenProse skill conventions * Align OpenProse skill with service system conventions * Fix OpenProse PR review inconsistencies * Clarify OpenProse state backend loading * Enforce OpenProse smoke run state gate
std/ops
Operational utilities for debugging, profiling, and validating OpenProse systems. These are the developer tools of the language -- the equivalent of git status, cargo check, and go vet. Each system maps to a prose CLI command.
Systems
| System | CLI Command | Description |
|---|---|---|
lint.prose.md |
prose lint <file> |
Validate structure, schema, shapes, and contract matching |
preflight.prose.md |
prose preflight <file> |
Check that dependencies are installed and environment variables are set |
wire.prose.md |
prose run std/ops/wire |
Run Forme wiring to produce an execution manifest |
status.prose.md |
prose status |
Show recent runs with system name, duration, and pass/fail status |
diagnose.prose.md |
prose run std/ops/diagnose |
Diagnose why a run failed -- root cause analysis with fix recommendations |
profiler.prose.md |
prose run std/ops/profiler |
Profile a run for cost, tokens, and time using actual API session data |
Two categories
Source-file tools operate on system *.prose.md files before execution:
lint-- validates that the system is well-formedpreflight-- validates that the runtime environment is readywire-- produces the execution manifest (Forme wiring)
Run-artifact tools operate on completed runs in .agents/prose/runs/:
status-- lists recent runs and their outcomesdiagnose-- investigates a failed run to find the root causeprofiler-- breaks down cost, time, and token usage from actual session data