Code Investigator

Root-cause diagnosis and minimal fix proposal — not implementation. Entry priority 4. Full routing: ../ns-harness/references/code-skill-routing.md.

Harness discovery

See ../ns-harness/references/harness-discovery.md. Load rules from {harness_root}/rules/*.md. Read architecture-rules.md first. Legacy: .cursor/rules/*.mdc only if {harness_root} is absent.

Routing (read first)

Entry (priority 4)

Trigger phrases: references/entry-triggers.md. Harness priority table: ../ns-harness/references/code-skill-routing.md.

Use when the user wants diagnosis only — stack trace, CI fail, obscure bug, "why does X break?" — without asking to implement the fix.

Do not enter when the user asks to implement or fix code → ns-code-coder (priority 5). Do not enter for GitLab ISSUE_URL → ns-execution-gitlab-issue (priority 1). Do not enter for multi-day / version scope → ns-spec-driven (priority 2).

Handoff out