cite-citadel: Skill for Claude Code

Open a PR

The one path from "the change is done" to "a green PR waiting on the human". Gate locally first, then push once. Every step below is runnable bash with an Expected: baseline so the first line that does not match names what broke. You never merge — you stop at green + resolved and hand the URL back.

0. Preconditions

• Work from the repo checkout on a feature branch (never commit to main).
• gh is authenticated (gh auth status) and uv sync has been run.
• Know the one-line topic of the change — it becomes the branch slug and the PR title.

1. Branch off main

Branch name is claude/<topic>-<slug> (kebab-case, no spaces). If you are already on such a branch with your work, skip the checkout.

git fetch origin
git checkout -b claude/doctor-billing-warning origin/main   # <topic>-<slug>, based on fresh main

Expected: Switched to a new branch 'claude/doctor-billing-warning'.

2. Route the diff (verify-corpus BEFORE the gates)

Look at what the diff touches — git diff --name-only origin/main...HEAD — and run the matching corpus verification before the local gates, because the offline suite does NOT exercise a real ingest:

The diff touches…	Run first
citadel/ingest.py, citadel/llm.py, or citadel/rules/**	/verify-corpus <affected-corpus> — minimally the corpus that stresses the change (see the table in that skill); all for a broad rules/ingest change
anything else (cli, store, viewer, docs, tests)	nothing extra — the offline suite covers it

verify-corpus spends a real ingest (minutes, your subscription), so scope it to the affected corpus, not all, unless the change is broad. A hard-gate failure there is a finding — fix it before pushing.

Expected: verify-corpus ends with a per-corpus PASS verdict (its hard gates hold).

3. Local gates (all four must pass)

Run them one at a time so a red one stops you immediately. Do not pipe pytest through tail inside an && chain — the pipe swallows pytest's exit code and a failing run looks green.