← all publishers

mikhin

@mikhin source repo

Report this profile Claim this profile

• 6 skills
• 0 followers
• 10 hours ago last updated

1. ▌
   Stack · mikhin

   What Yuri Mikhin already knows and how he verifies work — the frontend checking stack he runs on every change, how he reviews layout across viewports, and the product side of his own plugins and bots. Meant to be always on (SessionStart hook), not trigger-loaded.
   0 installs
2. ▌
   Review · mikhin

   Review the current branch, a PR or a commit — runs the built-in code-review at medium, then judges every finding against the code (accepted / rejected / ticket) and ends with a merge verdict. Also how Yuri Mikhin wants bugs investigated — the "why didn't the tests catch it" rule, test-before-fix order, anchored findings, what may block a merge, and when a review loop stops. Triggers — "/review", "review this", "findings", "what do you think of this review", "why is this flaky", "a bug in production", "another round", «ревью», «находки», «почему тесты не поймали», «ещё раунд».
   0 installs
3. ▌
   All Check · mikhin

   Run every check the project has except e2e, scoped to the files of the current PR or branch, and report one line per check. Triggers — "/all-check", "run all the checks", "all checks except e2e", "check the PR files", «запусти все проверки», «прогони проверки по файлам PR».
   0 installs
4. ▌
   Decisions · mikhin

   How Yuri Mikhin makes decisions — the questions he asks before accepting a change, where he expects answers to be looked up, and what he rejects on sight. Meant to be always on (SessionStart hook), not trigger-loaded.
   0 installs
5. ▌
   Jev · mikhin bundle

   Score the changed files of the current branch with Jev (typesafe-ai evaluation model via Vercel AI Gateway) — bug risk, logic in components, missing tests, published-snapshot writes. Triggers — "/jev", "run jev", "jev the diff", «прогони jev», «что скажет jev».
   0 installs
6. ▌
   Comms · mikhin

   How Yuri Mikhin writes to people outside the code — clients, product owners, teammates, plugin users. Draft first, never send; no blame, no hinted defects, no promises; one question instead of a pile of comments; copy-paste ready without quote marks. Triggers — "write to <person>", "reply to the client", "post a comment on the ticket", "send it in chat", "draft an answer", «напиши <имя>», «ответь клиенту», «отпиши в тикет», «черновик письма».
   0 installs