Skip to content

xonika9/agent-skills / .claude/skills/release

release

Verified

Use for this repository when the maintainer asks to prepare or publish a release — «подготовь релиз», «выпусти релиз», "prepare a release", "publish the release". Do not use for ordinary changelog edits, package validation, commits, pushes, or pull requests that are not explicitly a release.

Release

Prepare or publish a version of x9-agent-skills from the complete repository state. The latest public tag, the diff to the release candidate, CHANGELOG.md, both plugin manifests, the validation workflow, and the release workflow are the sources of truth; do not infer release scope from the current conversation or recent commits alone.

This is a private repository-local skill. Its canonical source is .claude/skills/release; .agents/skills exposes that source through a repository-relative symlink. Do not add it to the public skills/ package or its manifests and READMEs.

Select the mode

  • Prepare applies when the request is to prepare a release. Determine the calendar version, update release files, and run the release gate. Stop before commit, push, tag, or GitHub Release.
  • Publish applies only when the maintainer explicitly asks to publish or release. It includes preparation, a release commit, a push to main, and monitoring until the matching GitHub Release is visible or a concrete failure is reported.

An ordinary request to commit, push, merge, edit the changelog, or validate the package is not release authority. Never create or move a tag manually; .github/workflows/release.yml owns tag and GitHub Release creation after the pushed main commit passes validation.

Establish the candidate

Resolve the repository root from this skill's location, then inspect:

  • the worktree, current branch, remotes, and latest public v* tag;
  • the complete diff and commit range from that tag to the candidate, including uncommitted and untracked files;
  • README.md, README.ru.md, CHANGELOG.md, .claude-plugin/plugin.json, .codex-plugin/plugin.json;
  • the installed personal ~/.config/opencode/AGENTS.md, ~/.claude/CLAUDE.md, and ~/.codex/AGENTS.md plus their published sources in global-files/;
  • scripts/prepare_release.py, .github/workflows/validate.yml, and .github/workflows/release.yml.

Preserve unrelated and user-owned changes. If the candidate cannot be separated from unrelated work, the current branch cannot safely produce the intended main release, or the remote state conflicts with the local history, stop and report the exact blocker instead of rewriting history, discarding files, merging, or force-pushing.

Reconcile every user-visible change since the latest public tag with the release notes. Treat the AUDIT file list from python3 scripts/prepare_release.py --check as a backstop, not a substitute for reading the semantic diff.

Review onboarding contracts

From the diff since the latest public tag, identify every changed public skills/*/SKILL.md, every changed resource reachable from a public skill, and every added, modified, or deleted skills/*/references/onboarding.json. For each affected public skill, read its owner SKILL.md and the relevant reachable references to determine semantically whether an external operating prerequisite or a by-design runtime restriction was added, changed, or removed. Do not infer requirements with a heuristic parser, central registry, or hash gate.

Compare each finding with that skill's local references/onboarding.json using the declaration contract and validator owned by x9-onboarding. An added, modified, or deleted declaration is its own review trigger. For a deletion, read the owner even when its SKILL.md is unchanged and explicitly determine whether it now has no external operating prerequisites and runs in every runtime. A missing declaration is allowed only when the review finds neither.

Record an observable onboarding verdict for every affected public skill: MATCHED when the local declaration reflects its requirements and runtime restriction, NO_REQUIREMENTS when an absent declaration is justified, or BLOCKED when the declaration and semantic diff disagree. Include the changed surfaces and concise evidence in the release output. A BLOCKED verdict stops preparation until the contract or the candidate is corrected.

Prevent README drift

Read both READMEs completely and trace every public skill, installation route, compatibility claim, renamed concept, and removed behavior in the candidate to its documentation. A changed public contract must have an accurate corresponding section or an explicit, evidence-backed determination that the change has no README impact. Do not infer coverage from whether a README file appears in the diff.

Keep README.md as the canonical English presentation and README.ru.md materially equivalent. Update the English structure and facts first, then synchronize the Russian localization. Preserve verified commands, identifiers, links, and claims. Do not document this private release skill in either README.

Follow the Russian documentation contract for final editing and scanner verification.

Synchronize global instruction files

Load x9-agent-instructions, then compare the installed personal global files with the matching files under global-files/<harness>/. Preserve the byte-identical shared core and keep OpenCode-only, Codex-only, and Claude Code-only behavior in their respective runtime adapters.

Never copy credentials, personal paths, machine-specific state, private project names, or unverified runtime observations into global-files/. Keep the README descriptions and installation paths accurate in both languages.

Release authority permits reading the installed global files and updating their matching repository files; it does not permit replacing an independently managed file under a harness home directory. If the shared cores disagree or an installed file differs from its matching repository file unexpectedly, mark preparation BLOCKED instead of choosing a source.

Check personal skill links

A public skill without personal links stays invisible to the maintainer's local runtimes. On the Mac and on the Fedora machine reachable through the SSH alias x9-fedora, every skill under skills/ must be linked from ~/.agents/skills, and from ~/.claude/skills unless its references/onboarding.json restricts it to other runtimes; scripts/check_skill_links.py derives that exclusion from the declaration.

Release authority covers running the checker with --fix: it only adds missing links in each machine's established style and never replaces an existing entry. A wrong, broken, or stale entry, a skill not yet synced to Fedora, or an unreachable host keeps the gate BLOCKED until the maintainer resolves it.

Determine the version

Use YY.M.D.N without leading zeros in month, day, or sequence: Moscow's release date and a positive daily sequence starting at 1. Determine it from the fetched public tags with:

python3 scripts/prepare_release.py --next-version

Announce the computed number and continue within the requested Prepare or Publish authority; no separate version confirmation is needed. Follow calendar versioning for explicit versions, date boundaries, and immutable releases. Compatibility changes belong in the release notes, not in a semantic bump decision.

Prepare release files

With the selected calendar version:

  • move the populated Unreleased content into ## YY.M.D.N - YYYY-MM-DD, using the same date in the version and heading;
  • leave a new empty Unreleased template with Highlights, Install / update, Compatibility, and Breaking changes;
  • make the release notes concise and outcome-oriented, cover the complete candidate, and write None. explicitly when there are no breaking changes;
  • apply the identified README corrections, keeping the English and Russian versions materially equivalent;
  • synchronize the harness-specific files in global-files/ with the current personal global contracts;
  • set the same YY.M.D.N in both plugin manifests.

Do not include private paths, credentials, tokens, cookies, fabricated evidence, or changes outside the release candidate.

Release gate

Run the complete command set in checks.md. A failed command blocks preparation and publication until it is fixed or the maintainer explicitly changes scope; never present a partial gate as a successful release.

Preparation is complete when the release diff contains the selected version and date, both manifests agree, Unreleased is reset, the notes cover the tag-to-candidate diff, every public change is accurately represented in both READMEs or has a justified no-impact determination, the harness-specific global files match the current personal contracts, every public skill is linked on both machines, and every required check passes.

Publish

Publication requires all preparation conditions plus explicit publish authority. Commit the coherent release candidate without absorbing unrelated changes, push the release commit to main without force, and monitor the repository's validation and release workflows.

Publication is complete only when the GitHub Release for vYY.M.D.N is visible and points to the released commit. If a workflow fails, the tag points elsewhere, GitHub is unreachable, or the release does not appear after the workflows terminate, report the concrete state and stop without manufacturing or moving the tag.

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: 468kUpdated 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: 197kUpdated 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: 197kUpdated 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: 197kUpdated Claude CodeCodexVerifiedInstall