ce-patch

# Patch **Invocation input:** Change requested: $ARGUMENTS Make one genuinely small change with a short, predictable workflow. `/ce-patch` has one lane: a mechanical admission screen, a red-to-green edit within at most two candidate files, an external diff check, and one human acceptance gate. `--express` is accepted as a backward-compatible alias; it does not select different behavior. 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, including any test file the change needs. - **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 failing-then-passing check must fit inside the two-file boundary. If any of those facts cannot be established, route to `/ce-plan` without editing code. ## Execution Contract 1. **Screen before writing.** Run `patch-lint.py` over a transient candidate stub. Exit `1` (policy refusal) or `2` (inconclusive/error) both ro...