Skip to content

kozii-d/hover-translate / .claude/skills/release

release

Verified

Prepare a release of HoverTranslate — version, changelog, checks, live YouTube markup, store archives, and what the user uploads where. Uploads nothing itself.

Prepare release $0. Talk to the user in Russian. Nothing is uploaded or published: the user does that. Stop at the first failing step and report it.

1. May it go out

  • Read «Сейчас» in work/backlog.md: a release condition (a waiting window, a store still reviewing the previous version) that is not met — stop and say what is missing. A new upload replaces the one waiting in a store's review queue.
  • Tasks in review in work/backlog.md are not committed yet: list them and ask whether the release waits for them.
  • git status --short: uncommitted changes are the user's; list them.

2. Version and changelog

  • The number follows CLAUDE.md → «Releasing», judged by the CHANGELOG.md section: only Fixed → patch; Added or a change the viewer notices → minor; something the viewer loses → major. If $0 does not match, say so before changing anything.
  • npm run version:set -- $0, then the release date in the CHANGELOG.md heading (## [$0] - YYYY-MM-DD). Read the section as a viewer would: every entry says what changed for them.

3. Checks

npm run verify
npm run setup:chrome && npm run build && npm run test:e2e

4. YouTube's markup has not changed (~2 min, live YouTube)

node e2e/youtube-dom/capture.js
git diff --stat e2e/youtube-dom/captured

In the diff look at classes, nesting, position, z-index, pointer-events and what lies over the captions (onTopOfCaption); caption texts and small size shifts do not matter. If something the extension depends on changed, the fixtures in e2e/fixtures/ follow it and test:e2e runs again — that is a task of its own before the release, not a quick fix here. If nothing relevant changed, say so: The user discards the new capture himself (git checkout -- e2e/youtube-dom/captured; agents may not) or commits it with the release.

5. Old browsers

If a package that ships in the bundle or build.target changed since the last release (git diff <last tag>..HEAD -- package.json '*/package.json' '*/vite*.config.ts'; the tags are v1.1.9-style, git tag --sort=-v:refname | head -1), run the build in Chromium 102 and Firefox 115 by the recipe in CLAUDE.md → «Dependencies», in work/runs/release/, and delete the folder after.

6. Archives

npm run release

List every archive in releases/$0/ (unzip -l):

  • the store packages hold only manifest.json, _locales/, assets/icons/, extension/dist/, popup/dist/ (scripts/archive.js), and each manifest.json is its browser's (manifest.firefox.json in the .xpi), with version $0;
  • the source archive has no work/, .claude/, CLAUDE.md, .env, node_modules, dist, releases/.

7. For the user

In Russian:

  1. Manual check in a browser with the store-installed extension, after updating to the new package: one video with manual captions and one with auto-generated ones — hover, a Shift phrase, a click, «Translation saved», the dictionary in the popup. It is the only check of an update over a real store install.
  2. What goes where: Chrome Web Store — releases/$0/<chrome zip>; Edge Add-ons — the Edge zip; AMO — the .xpi plus the source archive. If the listing changed: npm run update:amo; if the screenshots were made again: npm run update:amo -- --screenshots (the user runs both — agents may not).
  3. A commit message for the version and the changelog date, in the style of git log (English, imperative).
  4. After the stores publish it: the dates go into «Сейчас» in work/backlog.md.

8. Clean up

When the user confirms the release is committed: the files of the tasks that went into it are deleted from work/tasks/, their lines from work/backlog.md; a decision worth keeping goes into work/decisions.md.

rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 466kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 196kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 196kUpdated Claude CodeCodexVerifiedInstall