메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | harness-ls-lint-setup |
| description | 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. |
/harness-setup Step 4.3 (ls-lint naming bootstrap).ls-lint.yml or harness-verify reports naming config drift.pi/harness/ls-lint/naming.manifest.json (global_rules, scoped_rules, ignores)| Role | Agent / command | Layer |
|---|---|---|
| Bootstrap | harness-ls-lint-bootstrap.mjs | Greenfield seed + first sync |
| Steward | harness/ls-lint-steward, /harness-ls-lint-steward | Proposes manifest changes (artifacts/ls-lint-manifest-proposal.yaml); chair applies |
| Sync | ls-lint-rules-sync.mjs, /harness-ls-lint-sync | Regenerates .ls-lint.yml from manifest after intent change |
| Observation | /harness-run, /harness-review | harness-ls-lint-cli.mjs → artifacts/ls-lint-signal.yaml |
Never auto-sync manifest from directory trees. Material manifest edits need steward evidence + chair approval.
| Path | Role |
|---|---|
.pi/harness/ls-lint/naming.manifest.json | Source of truth |
.ls-lint.yml | Generated ls-lint config (commit to git) |
.ls-lint/.harness-naming-meta.json | Sync metadata (gitignored) |
Custom YAML outside # --- harness:managed:start/end --- is preserved on every sync.
UP_PKG via .pi/scripts/README.md)| Situation | Command |
|---|---|
| First-time / harness-setup (idempotent) | node "$UP_PKG/.pi/scripts/harness-ls-lint-bootstrap.mjs" |
| After manifest edits | node "$UP_PKG/.pi/scripts/harness-ls-lint-bootstrap.mjs" --force |
| CI / verify only | node "$UP_PKG/.pi/scripts/ls-lint-rules-sync.mjs" --check |
| Run/review observation | node "$UP_PKG/.pi/scripts/harness-ls-lint-cli.mjs" or --json |
| In pi session | /harness-ls-lint-sync (extension; uses --force) |
harness-setup Step 2.9 or harness-cli-verify.sh).node "$UP_PKG/.pi/scripts/harness-ls-lint-bootstrap.mjs"
node "$UP_PKG/.pi/scripts/harness-ls-lint-cli.mjs" — fix violations or tune manifest rules/ignores..ls-lint.yml and project-specific naming.manifest.json.ls-lint-rules-sync.mjs, harness-ls-lint-bootstrap.mjs, harness-ls-lint-cli.mjsharness/ls-lint-stewardCommit 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.
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.
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.