change-analysis

# Change Analysis Run evidence-first analysis: truth, risk, next action before implementation, review, release, sync. ## Input Schema ```json { "question": "required analysis question", "scope": "required files, diff, issue text, report path, PR number, or repo area", "mode": "local|github|report|ecosystem", "done_when": "findings are source-backed, ranked, and have explicit confidence" } ``` ## Workflow Codex provides this selected `SKILL.md` path. Resolve `PLUGIN_ROOT` as the directory two levels above the containing skill directory, then use only helpers under `PLUGIN_ROOT/shared/` that are listed in `package-manifest.json`. Never guess a cache version or fall back to a source checkout. ### 01: Create run directory Run `python PLUGIN_ROOT/shared/create_run.py --skill change-analysis` once. Retain its single printed path as `<run-directory>` and substitute that literal path into every later artifact path and helper argument. Never store or reuse the path through a shell variable; shell variables do not persist across tool calls. ### 02: Normalize the analysis mode - `local`: code, local diff/reports, pasted text. - `github`: live issue/release/repository metadata through `github_read.py`; use only its audited built-in view groups (`gist`, `issue`, `pr`, `project`, `release`, `repo`, `ruleset`, `run`, `workflow`) or an explicit read-only GraphQL query for Discussions. PR collection uses `collect_pr.py` only. Prefer `gh`; use the public HTTPS fallback only as...