optimize-harness

/optimize-harness

Reads .claude/logs/*.jsonl (written by observe.py) and surfaces actionable suggestions: hooks to add, workflow gates to enable — based on what you actually do.

Does NOT repeat static analysis from /review. Hook binaries, MCP alignment, schema drift → run /shipwithai-starter:review. Runtime usage patterns (frequency, directories, commands) → run this skill.

Flag Handling

• --verbose — include LOW confidence suggestions (hidden by default)
• --window N — analysis window in days, minimum 7 (default: 30)
• --json — output as JSON instead of markdown report
• --force — bypass the 7-day cooldown advisory without prompting

Step 1 — Guard Clauses

Evaluate in order. Stop on first failure and output the message below.

Guard 1 — Observability not enabled:

Check: .claude/logs/ exists AND .claude/hooks/observe.py exists
Fail output:
  Observability not enabled. Run /shipwithai-starter:setup-observability
  first. optimize-harness requires at least 7 days of log data.

Guard 2 — Not enough data:

Check: ≥7 distinct YYYY-MM-DD log filenames within window
       AND ≥50 total parsed events
Fail output:
  Not enough data yet.
  Current: [N] days of logs, [T] tool calls
  Required: 7 days AND 50 tool calls
  Come back after [earliest_date + 7 days].

N = count of YYYY-MM-DD filenames within window. T = successfully parsed events.

Guard 3 — Cooldown (advisory only, not a hard block):

Check: starter-context.json → optimizer.last_run exists
       AND today - last_run < 7 days
Warn:  Last optimization was [N] days ago (last run: [date]).
       Results may not reflect new patterns. Run anyway? [y/N]

Proceed if user says yes, passes --force, or optimizer.last_run is absent.

Step 2 — Parse & Aggregate

Parse:

1. List .claude/logs/*.jsonl sorted by filename date; filter to window
2. Read line by line — skip malformed lines silently (no error output)
3. Discard: tool absent or not in {Edit, Write, Bash}
4. Discard: ts absent or unparseable