菜单
Run isolated Moraine dev sandbox validation. Use when testing ingest, MCP, monitor, ClickHouse schema, source formats, stack behavior, or any change where QA must not touch the developer's host ~/.moraine install; use before reporting completion for stack-facing changes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Help prepare and, only with explicit user approval, file a sanitized Moraine bug report for reproducible defects in Moraine itself.
Use Moraine realtime session data to inspect active agent work across harnesses when the user asks what is happening now or what another agent is doing.
Use Moraine MCP tools to recover prior agent-session context when the user refers to earlier work, decisions, failures, branches, files, or other agents.
Cut and publish Moraine releases from a version argument such as /release X.Y.Z or a request to use $moraine-dev:release. Use when Codex is asked to run Moraine's release process, bump release-managed versions, create and merge the release PR, push the vX.Y.Z tag, update GitHub release notes for a general audience, verify the release-moraine workflow, and confirm the PyPI moraine-cli package. Start or continue a Codex goal for the release.
Use Moraine MCP tools to recover prior agent-session context when the user refers to earlier work, decisions, failures, branches, files, or other agents.
Create Moraine pull requests on GitHub. Use when the branch is ready to open a PR; when the user asks to create, push, or open a PR; after local changes are committed; or when documenting user-facing features, bug fixes, performance optimizations, validation, changelog impact, or operational impact in a PR that follows repository conventions without AI attribution.
| name | moraine-sandbox-qa |
| description | Run isolated Moraine dev sandbox validation. Use when testing ingest, MCP, monitor, ClickHouse schema, source formats, stack behavior, or any change where QA must not touch the developer's host ~/.moraine install; use before reporting completion for stack-facing changes. |
Use the dev sandbox for stack-facing QA so validation runs against an isolated Moraine state directory and sibling ClickHouse service instead of the host install.
Use this workflow for changes touching:
crates/moraine-ingest-core/, ingest source formats, or fixtures.crates/moraine-mcp-core/, apps/moraine-mcp/, or MCP tool behavior.crates/moraine-monitor-core/, apps/moraine-monitor/, or web/monitor/.sql/, ClickHouse migrations, config templates, or stack lifecycle behavior.For docs-only or narrow metadata changes, normal local checks are usually enough.
Boot from the authoritative worktree for the change. Use --quiet; do not pipe moraine-sandbox up through tail or head.
id=$(scripts/dev/sandbox/moraine-sandbox up --quiet)
echo "sandbox: $id"
scripts/dev/sandbox/moraine-sandbox status "$id"
If you spawned from an isolation worktree, compare with the parent or sibling feature worktree first. Boot the sandbox from the worktree that contains the actual in-progress code.
Use the sandbox shell for cargo and stack checks:
scripts/dev/sandbox/moraine-sandbox shell "$id"
cd /repo
cargo fmt --all -- --check
cargo test -p <crate> --locked
cargo test --workspace --locked
cargo clippy --workspace --all-targets -- -D warnings
Choose focused tests first, then broaden according to risk. For changes that affect ingest, MCP, monitor routes, or schema behavior, run the functional stack smoke test when feasible:
bash scripts/ci/e2e-stack.sh
Check the monitor health endpoint using the sandbox-reported port:
port=$(scripts/dev/sandbox/moraine-sandbox status "$id" | awk -F: '/^\[sandbox\] monitor/{print $NF}')
curl -fsS "http://127.0.0.1:${port}/api/v1/health"
For MCP tool surface changes or release-level confidence, consider scripts/dev/sandbox/agent-smoke-e2e --help. It requires ANTHROPIC_API_KEY.
Always tear down the sandbox before reporting the task complete:
scripts/dev/sandbox/moraine-sandbox down "$id"
Final reporting should include the sandbox id, commands run, outcomes, and confirmation that down "$id" succeeded. If sandbox QA was expected but not run, explain why.