whats2000

Use when writing or editing ANY PaperHub agent/LLM prompt YAML — BOTH a DEPLOYMENT prompt (backend/src/paperhub/llm/prompts/*.yaml system/user template) AND an EVAL/EXPERIMENT variant (backend/benchmark/agent/prompts/<stage>/<version>.yaml driven by the agent benchmark sweep) — a new agent/router/synthesizer/subagent stage, or any change to how a model is instructed. Fires whenever you are tempted to hand-write one prompt and ship it, tweak a single prompt line "obviously," or adopt a rewrite without comparing it against the current one across multiple queries. Experiment/benchmark variants are NOT exempt: they get the SAME discipline (>=2 variants x query set x judged comparison; concise, direct, minimal-token rewrites), never a one-off draft.

Use when the user signals a feature/hotfix branch is ready to merge into main on the PaperHub repo (phrases like "ready to merge", "merge prep", "let's land this hotfix", "release this branch") OR when invoked via the /paperhub-merge-prep slash. Do NOT fire on code-level "merge these functions" / git-conflict resolution / cherry-pick discussions.

PaperHub OVERRIDE of the generic branch-finish flow. Use when completing/finishing/landing a development branch in the PaperHub repo — "ready to merge", "finish the branch", "wrap up the work", "complete this", "merge to main", "release this branch", or whenever you would otherwise reach for superpowers:finishing-a-development-branch. It REQUIRES running paperhub-merge-prep FIRST so the release files (4 README locales, version bumps + lockfiles, SRS revision row, CLAUDE.md pointers) are updated before any merge/PR/push — the generic skill skips those and they get missed.

ALWAYS use BEFORE running `git commit --amend` (every time, any commit, any branch, any repo) — and before any other history-rewriting git command (`git rebase`, a `git reset` that drops/rewrites a commit, `git push --force`/`--force-with-lease`). Decides whether the rewrite is safe (the target commit is NOT yet on the remote → amend/rewrite allowed) or prohibited (the commit IS already pushed → rewriting it forces a force-push, which is banned → stack a NEW commit instead). This is NOT tied to release/merge work — it applies to ANY amend. Fires on phrases like "amend", "fix up the last commit", "squash", "rebase", "redo that commit".

Use when writing or editing source files inside an `experiments/expNN_*/eNNx/` cell directory, or about to add a `_lib/` / `utils/` / `helpers/` directory under `experiments/` — enforces root-canonical filename rule (cell source files must mirror project-root filenames), forbids shared helper directories, and gates function reuse to two options: import unmodified from root, or copy the entire root file into the cell and edit the copy.

Use when creating a new experiment directory, adding a variant cell, or tempted to rename / delete / edit a prior `experiments/expNN_*` directory — enforces next-unused-number rule, prior-experiments-are-read-only, variant naming `eNNa/b/c…`, and the principle that reservations are not free for re-use.

Use when designing a new experiment (read `experiments/NOTES.md` first to avoid repeating known-failed approaches), when a cell has finished and its metrics are committed (append an entry), or when correcting a wrong number in a prior entry (in-place fix is allowed and often required — leaving a wrong number on the page poisons future context; preserve the trail with strikethrough or a correction note when feasible, but accuracy of current evidence comes first) — enforces read-before-design, append-only-after-completion, every number traceable to an actual run (no estimates, no assumptions, no projected numbers), and root-cause hypotheses for every failed variant.