ce-patchlisted

# Patch **Invocation input:** Change requested: $ARGUMENTS Make one genuinely small change with a short, predictable workflow. `/core-engineering:ce-patch` has one lane: a mechanical admission screen, a mode-appropriate before/after proof within at most two candidate files, an external diff check, and one human acceptance gate. This skill creates no plan, spec, task, eligibility, or verification bundle. Its only durable workflow record is one append-only line written after the human accepts. ## Runtime Inputs - **Change request (required):** the behavior or text to change. - **Candidate files (discovered or supplied):** at most two repository-relative paths. Behavior mode includes its focused test file; content mode may use one target file when the proof is an external deterministic command. - **Repository evidence (read-only):** the candidate files, their direct callers or consumers (one hop), relevant test/build commands, `git status`, and other plans' `tasks.json` ownership declarations under `docs/plans/`. - **Diff base:** the current git commit captured before any patch-owned edit. The repository must be a git worktree, the candidate set must be enumerable, and a meaningful mode-appropriate proof must exist. Otherwise route to `/core-engineering:ce-plan` without editing. ## Execution Contract 1. **Screen before writing.** Run `patch-lint.py` over a transient candidate stub. Exit `1` (policy refusal) or `2` (inconclusive/error) both route directly to