メニュー
Compile task-specific harness context using context-mode and graphify. Use for architecture questions, large codebase context before harness-plan or harness-run. NEVER use lean-ctx on harness paths.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | harness-context |
| description | Compile task-specific harness context using context-mode and graphify. Use for architecture questions, large codebase context before harness-plan or harness-run. NEVER use lean-ctx on harness paths. |
/harness-plan, /harness-run, or /harness-autoctx_read, ctx_search, etc.) on harness paths — locked by Phase 2 plan.Use these in rough priority order — not every tool on every task:
| Need | Tool |
|---|---|
| Architecture, god nodes, cross-file relationships | graphify-out/GRAPH_REPORT.md, graphify query, graphify explain, graphify path |
| Structural code patterns | sg -p '…' (ast-grep) |
| Semantic implementation search | ccc search (harness pre-indexes before subprocess spawns) |
| File detail | context-mode maps/signatures, then targeted reads |
| Harness governance | approved policies and decision logs in the target project |
For /harness-plan Phase 1, parent compiles findings into artifacts/planning-context.yaml — see harness-plan skill.
Compact context block:
./raw/ is graphify source storage; run graphify update . after significant harness code changes.Commit staged git changes with configurable message format and Co-authored-by trailer from .pi/auto-commit.json. Use when the user asks to commit, when /harness-auto or harness run completion requires a commit, or before any git commit — never use raw git commit -m.
Plan-phase Review Gate debate — pi-messenger threads, lane YAML, bus tools for parent orchestrator.
Structured user decisions via ask_user for harness setup, planning, and governance forks. Use with /harness-setup, /harness-plan, harness-auto plan phase, and when agents emit human_required.
Deprecated — use harness-review skill and /harness-review for the full post-run gate. This file remains as a pointer for older prompts.
Enforce harness governance phases, policy gates, budgets, and promotion rules. Use during execute, evaluate, merge, or when interpreting policy-gate / budget-guard messages.
Bootstrap ls-lint filename rules for harness projects — seed naming.manifest.json, generate merge-safe .ls-lint.yml, and document bootstrap vs --force sync. Use during /harness-setup, when adding ls-lint to a repo, or when .ls-lint.yml is missing or out of date.