seekter-gitlisted

# /seekter-git — ship the kit, never the candidate Seekter's repository holds two things that must never mix. | | Tracked, shareable | Ignored, private | |---|---|---| | What | `.claude/skills/`, `reference/`, `scripts/`, `templates/`, `README.md`, `CLAUDE.md` | `profile/`, `applications/`, `runs/` | | Whose | The kit. Works for any candidate. | This candidate. Works for nobody else. | **This skill only ever commits the left column.** `.gitignore` already covers the right one, but a `.gitignore` protects paths, not *content*: the real risk is a candidate's phone number quoted inside `reference/ats-mechanics.md` as an example. That has already happened once (25 Sept, six separate places), so the leak scan in §2 is the point of this skill, not the ceremony around it. ## 0. Only run when there is kit work to ship ```bash git status --short git diff --stat ``` Nothing under `profile/`, `applications/` or `runs/` may appear. If it does, **stop**: either `.gitignore` is broken or something was force-added. Fix that first and say so. If the only changes are to ignored paths, there is nothing to ship. Say that and stop; a run that logged 8 applications and taught the kit nothing is a normal day. ## 1. Read the diff before describing it ```bash git diff ``` Read it properly. The commit message is a claim about what changed, and the house style (§4) is a claim about *what was learned*, which you cannot write from a file list. ## 2. Leak scan — the part that matters Build th