Agent skill

Doc View Release Readiness

by liuzhihang in liuzhihang/doc-view

A skill your agent uses when preparing, checking, or reviewing a Doc View plugin release, including changelog, version, plugin verification, manual IDE validation, Marketplace preparation, and…

MITAuto-check passedProduct & Project Management

Install Doc View Release Readiness

skills CLI
$ npx skills add liuzhihang/doc-view --skill doc-view-release-readiness -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install liuzhihang/doc-view doc-view-release-readiness --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/liuzhihang/doc-view.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/doc-view-release-readiness .claude/skills/doc-view-release-readiness && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
doc-view-release-readiness
GitHub stars
207
Token cost
~494 tokens
SKILL.md length
210 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when preparing, checking, or reviewing a Doc View plugin release, including changelog, version, plugin verification, manual IDE validation, Marketplace preparation, and…

  • Works in 7 steps: Identify release scope and included… → Check version, changelog, branch/tag… → Inspect staged/unstaged/untracked diff… → …
  • Reviewing a Doc View plugin release
  • SKILL.md covers Read First, Steps and Guardrails
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Doc View Release Readiness is an agent skill from liuzhihang/doc-view. Use when preparing, checking, or reviewing a Doc View plugin release, including changelog, version, plugin verification, manual IDE validation, Marketplace preparation, and rollback notes.

Its SKILL.md is about 490 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering Feature launches and release readiness and Changelog and release notes. It works with JetBrains IDEs and Gradle. The repository describes itself as: IDEA 插件 Doc View 的仓库地址. The licence is MIT.

When your agent uses it

  • Reviewing a Doc View plugin release
  • Including changelog
  • Plugin verification
  • Manual IDE validation

Example prompts

  • “/doc-view-release-readiness”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Identify release scope and included changes; confirm tasks are complete and required specs are synced/archived or explicitly pending.
  2. Check version, changelog, branch/tag target, Marketplace/GitHub release expectations, and rollback version.
  3. Inspect staged/unstaged/untracked diff for unintended runtime, descriptor, dependency, resource, generated, or secret-bearing files.
  4. Select and run exact automatic/manual validation from the release checklist; distinguish real tests from 0 tests or cache-only results.
  5. Inspect Plugin Verifier compatibility/internal/deprecated findings and the actual IDE matrix.
  6. Confirm tokens and private endpoints stay outside the repo and logs.
  7. Record artifact SHA, skipped validation, residual risks, post-release checks, and rollback notes.

What it can do on your machine

Read from SKILL.md and the folder at commit 00f1f94. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Doc View Release Readiness loads about 494 tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 210 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~54
When it runs · the whole SKILL.md, loaded when a task matches
~494

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from liuzhihang/doc-view at commit 00f1f94, republished under its MIT licence (© liuzhihang). 210 words, ~494 tokens.

Download SKILL.mdSave it as .claude/skills/doc-view-release-readiness/SKILL.md (or your agent's skills folder).
name
doc-view-release-readiness
description
Use when preparing, checking, or reviewing a Doc View plugin release, including changelog, version, plugin verification, manual IDE validation, Marketplace preparation, and rollback notes.

Doc View Release Readiness

Use this skill before publishing or declaring a release candidate ready. docs/release-checklist.md is the authoritative validation matrix.

Read First

  • AGENTS.md
  • docs/release-checklist.md
  • CHANGELOG.md
  • gradle.properties, build.gradle, Gradle wrapper, and plugin.xml
  • OpenSpec status/context for every change included in the release
  • docs/intellij-compatibility.md for IntelliJ API/platform changes or full release compatibility review

Steps

  1. Identify release scope and included changes; confirm tasks are complete and required specs are synced/archived or explicitly pending.
  2. Check version, changelog, branch/tag target, Marketplace/GitHub release expectations, and rollback version.
  3. Inspect staged/unstaged/untracked diff for unintended runtime, descriptor, dependency, resource, generated, or secret-bearing files.
  4. Select and run exact automatic/manual validation from the release checklist; distinguish real tests from 0 tests or cache-only results.
  5. Inspect Plugin Verifier compatibility/internal/deprecated findings and the actual IDE matrix.
  6. Confirm tokens and private endpoints stay outside the repo and logs.
  7. Record artifact SHA, skipped validation, residual risks, post-release checks, and rollback notes.

Guardrails

  • Do not run publishPlugin, push tags, create a release, merge master, or rotate external credentials unless the maintainer explicitly authorizes it.
  • Do not treat documentation checks, compilation, or zero discovered tests as runtime coverage.
  • Do not publish with unresolved compatibility problems or exposed credentials.
  • Do not expose tokens, cookies, private endpoints, or sensitive payloads in reports.

© liuzhihang, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .codex/skills/doc-view-release-readiness of liuzhihang/doc-view.

Open the folder on GitHubat commit 00f1f94

Compare with similar skills

Doc View Release Readiness next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Doc View Release Readiness compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Doc View Release Readiness this skillliuzhihang/doc-view207—~494Automated safety check: PassMIT
Release Readiness Reviewkernitus/BukkitOldCombatMechanics225—~1.5kAutomated safety check: PassMPL-2.0
AppsFlyer Unity Plugin Release CheckAppsFlyerSDK/appsflyer-unity-plugin178—~470Automated safety check: PassMIT
Release ReadinessRunoreLab/MahoShojo-Generator166—~342Automated safety check: PassApache-2.0
Gf Releasecodejunkie99/Gateflow-Plugin117—~676Automated safety check: PassCustom licence
Feature Launch Playbookgooseworks-ai/goose-skills1.2k1 repos~1.8kAutomated safety check: PassMIT

Similar skills

  • Release Readiness Review

    kernitus/BukkitOldCombatMechanics

    A skill your agent uses for GitHub release, Hangar, CurseForge/BukkitDev upload, Spigot release handoff, licence, asset naming, supported-version, and workflow readiness checks; do not use for…

    225 GitHub stars~1.5k tokensUpdated 7 days ago
    Product & Project ManagementAuto-check passed
  • AppsFlyer Unity Plugin Release Check

    AppsFlyerSDK/appsflyer-unity-plugin

    Reviews the AppsFlyer Unity plugin before a release: version consistency, changelog, Android and iOS parity, billing variants and .unitypackage freshness.

    178 GitHub stars~470 tokensUpdated 6 days ago
    DevelopmentAuto-check passed
  • Release Readiness

    RunoreLab/MahoShojo-Generator

    A skill your agent uses when preparing or reviewing a MahoShojo-Generator version release, release candidate, changelog/docs readiness, deployment impact, migration notes, or final pre-release…

    166 GitHub stars~342 tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Gf Release

    codejunkie99/Gateflow-Plugin

    GateFlow release readiness workflow. An agent skill from codejunkie99/Gateflow-Plugin.

    117 GitHub stars~676 tokensUpdated 24 days ago
    Product & Project ManagementAuto-check passed
  • Feature Launch Playbook

    gooseworks-ai/goose-skills

    Take a new feature or product update and generate the full launch kit: changelog entry, email announcement, LinkedIn post variants, in-app banner text, Twitter/X thread, and internal sales…

    1.2k GitHub starsUsed in 1 repo~1.8k tokens
    Product & Project ManagementAuto-check passed
  • Audit herdr release readiness by comparing commits since the base release against next-release changelog and docs. Use when asked to run or apply the repo's…

    43k GitHub stars~289 tokensUpdated 2 days ago
    DevelopmentAuto-check passed

More from liuzhihang/doc-view

  • Doc View Contract Design

    liuzhihang/doc-view

    A skill your agent uses when defining or reviewing Doc View behavior contracts before changing PSI parsing, DTOs, Markdown output, uploads, exports, settings, UI-visible behavior, or IntelliJ…

    207 GitHub stars~539 tokensUpdated 24 days ago
    Auto-check passed
  • Doc View Docs Maintenance

    liuzhihang/doc-view

    A skill your agent uses when creating or updating Doc View repository documentation, AGENTS.md, AI workflow guidance, OpenSpec configuration, or repo-local Codex skills.

    207 GitHub stars~456 tokensUpdated 24 days ago
    Auto-check passed
  • Doc View Java Maintenance

    liuzhihang/doc-view

    A skill your agent uses when implementing or reviewing Java-only Doc View production changes, especially PSI parsing, services, DTOs, UI, integrations, settings, export, or IntelliJ Platform behavior.

    207 GitHub stars~557 tokensUpdated 24 days ago
    Auto-check passed

Questions about Doc View Release Readiness

What does Doc View Release Readiness do?

A skill your agent uses when preparing, checking, or reviewing a Doc View plugin release, including changelog, version, plugin verification, manual IDE validation, Marketplace preparation, and…. Doc View Release Readiness is an agent skill from liuzhihang/doc-view. Use when preparing, checking, or reviewing a Doc View plugin release, including changelog, version, plugin verification, manual IDE validation, Marketplace preparation, and rollback notes.

When should I use Doc View Release Readiness?

Doc View Release Readiness fits situations like: reviewing a Doc View plugin release; including changelog; plugin verification; manual IDE validation.

How do I install Doc View Release Readiness in Claude Code?

Run `npx skills add liuzhihang/doc-view --skill doc-view-release-readiness -a claude-code`. Or copy the skill folder (.codex/skills/doc-view-release-readiness in liuzhihang/doc-view) into .claude/skills/doc-view-release-readiness in your project. Claude Code loads it when a task matches its description.

How do I install Doc View Release Readiness in Codex?

Run `npx skills add liuzhihang/doc-view --skill doc-view-release-readiness -a codex`. Or copy the skill folder (.codex/skills/doc-view-release-readiness in liuzhihang/doc-view) into .agents/skills/doc-view-release-readiness in your project. Codex loads it when a task matches its description.

Can I use Doc View Release Readiness in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add liuzhihang/doc-view --skill doc-view-release-readiness -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/doc-view-release-readiness, .gemini/skills/doc-view-release-readiness, .github/skills/doc-view-release-readiness and .opencode/skills/doc-view-release-readiness in your project.

What does Doc View Release Readiness need to run?

SKILL.md names no scripts, command-line tools or credentials: Doc View Release Readiness is instructions for the agent only.

Does Doc View Release Readiness access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Doc View Release Readiness safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Doc View Release Readiness use?

Doc View Release Readiness is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Doc View Release Readiness use?

About 494 tokens (SKILL.md is roughly 2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Doc View Release Readiness?

Skills that share tags, products or a category with Doc View Release Readiness: Release Readiness Review (kernitus/BukkitOldCombatMechanics, 225 stars), AppsFlyer Unity Plugin Release Check (AppsFlyerSDK/appsflyer-unity-plugin, 178 stars), Release Readiness (RunoreLab/MahoShojo-Generator, 166 stars) and Gf Release (codejunkie99/Gateflow-Plugin, 117 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Doc View Release Readiness?

liuzhihang (a GitHub user) maintains it in liuzhihang/doc-view, which has 207 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on September 16, 2026.

Source: liuzhihang/doc-view on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.