Weekly maintenance sweep that restores RAII symmetry in the YANET2 C code. The convention is four orthogonal primitives: new allocates ONLY the struct, init fills fields (and on any error jumps to a single err: label that calls fini), fini releases ONLY field memory and is idempotent, free deallocates ONLY the struct and is NULL-safe — paired new<->free and init<->fini. The sweep has two axes: a NAMING axis (misnamed/non-canonical destructors, found by scan.sh) and a STRUCTURAL axis (init error-path leaks/double-free/UAF, non-idempotent fini, non-NULL-safe free, new/free orthogonality, found by structural-scan.sh plus the leak-hunt workflow). It fixes a bounded batch per run, one prefix family per PR, with a persistent ledger. Use whenever the user invokes the weekly RAII sweep, asks to "fix RAII symmetry", "приведи lifecycle-функции к паттерну", "найди несимметричные init/fini", "сделай fini/free идемпотентными", wants the single-err-label init discipline, or wants a C lifecycle cleanup pass.
The canonical publish/merge runbook for landing a verified change on main: branch from confirmed origin/main, stage ONLY the intended files, open a scoped PR (no Claude footers), drive CI to green, address EVERY review/Codex finding, and merge with the correct squash/rebase strategy — then clean up the branch and worktree. Use this skill WHENEVER the user asks to ship, land, publish, or merge work: "create a PR", "open a PR", "create and merge", "ship this", "land this change", "оформи PR", "сделай PR", "залей", "влей в main", "добейся вливания в main", "смержи", or any time finished, reviewer-approved code needs to reach main. Covers parallel PRs, stacked PRs, prerequisite- refactor splits, workflow-file OAuth scope, CI-flake reruns, and the recovery recipes when a push/merge goes wrong.
De-duplicate the YANET2 web/ frontend (TypeScript/React/SCSS) by finding copy-pasted code across pages and extracting it into shared components, hooks, SCSS, and utils — then proving the refactor is visually identical and shipping one PR per extraction. Use this skill WHENEVER the user asks to "find the common parts", "extract shared components", "pull out the duplicated code", "DRY up the pages", "this got copy-pasted between pages", "decompose the web code", or runs a cleanup pass after a large web feature push — even if they never say the word "dedup". It is the right tool any time the goal is reducing duplication in web/src.