菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/eric-tramel/moraine --skill moraine-sandbox-qa命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Search and inspect prior agent sessions, observe active agent work, or prepare a sanitized Moraine bug report through the local Moraine MCP server.
Cut and publish Moraine releases from a version argument such as /release X.Y.Z in Kiro or a request to use $moraine-dev:release in Codex. Use when Codex or Kiro 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. In Codex, start or continue a durable goal for the release.
Coordinate a delegated full multi-persona code review for a Moraine PR or local change. Use when asked to review a PR, run review agents, get code review feedback, or iterate on review feedback using all CodeReview personas: elegance, idiom, correctness, completeness, security, YAGNI, and scope. Invoking this skill is an explicit request to launch reviewer subagents.
基于 SOC 职业分类
正在显示 SKILL.md
| 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.