Release Plugin
flutter/flutter-intellij
Prepare and execute a new release for the flutter-intellij plugin, including updating dependencies, compatibility bounds, changelogs, and verification.
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.
MITAuto-check passed
Install Doc View Java Maintenance
$ npx skills add liuzhihang/doc-view --skill doc-view-java-maintenance -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install liuzhihang/doc-view doc-view-java-maintenance --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-java-maintenance .claude/skills/doc-view-java-maintenance && rm -rf skills-srcUse ~/.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/
Install the "doc-view-java-maintenance" agent skill from https://github.com/liuzhihang/doc-view/tree/master/.codex/skills/doc-view-java-maintenance into .claude/skills/doc-view-java-maintenance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-view-java-maintenance", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/liuzhihang/doc-view/tree/master/.codex/skills/doc-view-java-maintenanceType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add liuzhihang/doc-view --skill doc-view-java-maintenance -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install liuzhihang/doc-view doc-view-java-maintenance --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/liuzhihang/doc-view.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/doc-view-java-maintenance .agents/skills/doc-view-java-maintenance && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "doc-view-java-maintenance" agent skill from https://github.com/liuzhihang/doc-view/tree/master/.codex/skills/doc-view-java-maintenance into .agents/skills/doc-view-java-maintenance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-view-java-maintenance", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add liuzhihang/doc-view --skill doc-view-java-maintenance -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install liuzhihang/doc-view doc-view-java-maintenance --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/liuzhihang/doc-view.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/doc-view-java-maintenance .cursor/skills/doc-view-java-maintenance && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "doc-view-java-maintenance" agent skill from https://github.com/liuzhihang/doc-view/tree/master/.codex/skills/doc-view-java-maintenance into .cursor/skills/doc-view-java-maintenance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-view-java-maintenance", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/liuzhihang/doc-view.git --path .codex/skills/doc-view-java-maintenance--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add liuzhihang/doc-view --skill doc-view-java-maintenance -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install liuzhihang/doc-view doc-view-java-maintenance --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/liuzhihang/doc-view.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/doc-view-java-maintenance .gemini/skills/doc-view-java-maintenance && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "doc-view-java-maintenance" agent skill from https://github.com/liuzhihang/doc-view/tree/master/.codex/skills/doc-view-java-maintenance into .gemini/skills/doc-view-java-maintenance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-view-java-maintenance", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install liuzhihang/doc-view doc-view-java-maintenanceInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add liuzhihang/doc-view --skill doc-view-java-maintenance -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/liuzhihang/doc-view.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/doc-view-java-maintenance .github/skills/doc-view-java-maintenance && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "doc-view-java-maintenance" agent skill from https://github.com/liuzhihang/doc-view/tree/master/.codex/skills/doc-view-java-maintenance into .github/skills/doc-view-java-maintenance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-view-java-maintenance", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add liuzhihang/doc-view --skill doc-view-java-maintenance -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install liuzhihang/doc-view doc-view-java-maintenance --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/liuzhihang/doc-view.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/doc-view-java-maintenance .opencode/skills/doc-view-java-maintenance && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "doc-view-java-maintenance" agent skill from https://github.com/liuzhihang/doc-view/tree/master/.codex/skills/doc-view-java-maintenance into .opencode/skills/doc-view-java-maintenance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-view-java-maintenance", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
doc-view-java-maintenance- GitHub stars
- 207
- Token cost
- ~557 tokens
- SKILL.md length
- 252 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
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.
- Works in 8 steps: Confirm the active OpenSpec change… → Locate the narrow package boundary:… → Write the failing contract test or… → …
- Reviewing Java-only Doc View production changes
- 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 Java Maintenance is an agent skill from liuzhihang/doc-view. Use when implementing or reviewing Java-only Doc View production changes, especially PSI parsing, services, DTOs, UI, integrations, settings, export, or IntelliJ Platform behavior.
Its SKILL.md is about 560 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with Java and JetBrains IDEs. The repository describes itself as: IDEA 插件 Doc View 的仓库地址. The licence is MIT.
When your agent uses it
- Reviewing Java-only Doc View production changes
- Especially PSI parsing
- IntelliJ Platform behavior
Example prompts
- “/doc-view-java-maintenance”
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Confirm the active OpenSpec change authorizes runtime files and defines expected behavior and validation.
- Locate the narrow package boundary: service, utils, dto, ui, integration, config, provider, or action.
- Write the failing contract test or fixture before production code.
- Preserve Java-only production code and prefer existing services, DTOs, utilities, and public IntelliJ API patterns.
- For PSI changes, validate Spring/Feign/Dubbo impact as applicable and guard recursion, invalid elements, Dumb Mode, read actions, and…
- For UI/action work, keep update lightweight and heavy work off EDT.
- For integration work, protect secrets and make authentication/network/server failures understandable.
- Implement the smallest change, run targeted then full verification, and update OpenSpec tasks only after success.
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 Java Maintenance loads about 557 tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 252 words of instructions outside code blocks.
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). 252 words, ~557 tokens.
Download SKILL.mdSave it as
.claude/skills/doc-view-java-maintenance/SKILL.md (or your agent's skills folder).- name
- doc-view-java-maintenance
- description
- Use when implementing or reviewing Java-only Doc View production changes, especially PSI parsing, services, DTOs, UI, integrations, settings, export, or IntelliJ Platform behavior.
Doc View Java Maintenance
Use this skill for production plugin work after an observable behavior contract is apply-ready.
Read First
AGENTS.mddocs/architecture.md- Every active apply
contextFilespath returned by OpenSpec; runtime work requires proposal/design/spec/tasks context docs/contract-design.mdfor PSI, DTO, Markdown, upload, export, settings, writeback, or UI behaviordocs/performance-guide.mdfor PSI, recursion, cache, background task, rendering, export, upload, or UI responsivenessdocs/intellij-compatibility.mdfor IntelliJ API, Gradle platform, descriptor, extension, or compatibility work
Steps
- Confirm the active OpenSpec change authorizes runtime files and defines expected behavior and validation.
- Locate the narrow package boundary:
service,utils,dto,ui,integration,config,provider, oraction. - Write the failing contract test or fixture before production code.
- Preserve Java-only production code and prefer existing services, DTOs, utilities, and public IntelliJ API patterns.
- For PSI changes, validate Spring/Feign/Dubbo impact as applicable and guard recursion, invalid elements, Dumb Mode, read actions, and project disposal.
- For UI/action work, keep
updatelightweight and heavy work off EDT. - For integration work, protect secrets and make authentication/network/server failures understandable.
- Implement the smallest change, run targeted then full verification, and update OpenSpec tasks only after success.
Guardrails
- Do not change generated Markdown shape, payloads, settings, UI, or compatibility without matching OpenSpec requirements.
- Do not modify
plugin.xml, Gradle, dependencies, or resources unless the approved change explicitly requires them. - Do not add Kotlin, Groovy, scripts, generated runtime sources, or new production languages.
- Do not mark tasks complete before code and exact verification are complete.
- Do not revert unrelated user changes.
© 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-java-maintenance of liuzhihang/doc-view.
Open the folder on GitHubat commit 00f1f94
Compare with similar skills
Doc View Java Maintenance 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Doc View Java Maintenance this skillliuzhihang/doc-view | 207 | — | ~557 | Automated safety check: Pass | MIT | |
| Release Pluginflutter/flutter-intellij | 2k | — | ~1k | Automated safety check: Pass | BSD-3-Clause | |
| Amplicode InstallAmplicode/spring-skills | 126 | — | ~2.6k | Automated safety check: Pass | None | |
| Idea MCPdtprj/dongting | 208 | — | ~698 | Automated safety check: Pass | Apache-2.0 | |
| Ij Debuggerxpinjection/test-driven-spring-boot | 112 | — | ~6.4k | Automated safety check: Pass | MIT | |
| Debug Surefireeclipse-rdf4j/rdf4j | 420 | — | ~2.4k | Automated safety check: Pass | BSD-3-Clause |
Similar skills
Amplicode Install
Amplicode/spring-skills
Installs the Amplicode IntelliJ plugin into IntelliJ IDEA (Ultimate/Community) and GigaIDE on the user's machine.
Idea MCP
dtprj/dongting
IntelliJ IDEA MCP for Java code analysis, testing, refactoring, and project navigation.
Ij Debugger
xpinjection/test-driven-spring-boot
Debugger-first runtime root-cause analysis for JVM code in IntelliJ IDEA.
Debug Surefire
eclipse-rdf4j/rdf4j
Debug Maven Surefire unit tests by running them in JDWP "wait for debugger" mode (-Dmaven.surefire.debug) and attaching to the forked test JVM using jdb (preferred for CLI/agent debugging)…
Kotlin Tooling Kotlin Toolchain
Kotlin/kotlin-agent-skills
Load when building, running, testing, packaging, linting, or configuring a Kotlin/Java project with the Kotlin Toolchain (JetBrains' unified CLI, formerly Amper), when scaffolding a new or…
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…
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.
Doc View Release Readiness
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…
Related
Works with
Questions about Doc View Java Maintenance
What does Doc View Java Maintenance do?
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. Doc View Java Maintenance is an agent skill from liuzhihang/doc-view. Use when implementing or reviewing Java-only Doc View production changes, especially PSI parsing, services, DTOs, UI, integrations, settings, export, or IntelliJ Platform behavior.
When should I use Doc View Java Maintenance?
Doc View Java Maintenance fits situations like: reviewing Java-only Doc View production changes; especially PSI parsing; intelliJ Platform behavior.
How do I install Doc View Java Maintenance in Claude Code?
Run `npx skills add liuzhihang/doc-view --skill doc-view-java-maintenance -a claude-code`. Or copy the skill folder (.codex/skills/doc-view-java-maintenance in liuzhihang/doc-view) into .claude/skills/doc-view-java-maintenance in your project. Claude Code loads it when a task matches its description.
How do I install Doc View Java Maintenance in Codex?
Run `npx skills add liuzhihang/doc-view --skill doc-view-java-maintenance -a codex`. Or copy the skill folder (.codex/skills/doc-view-java-maintenance in liuzhihang/doc-view) into .agents/skills/doc-view-java-maintenance in your project. Codex loads it when a task matches its description.
Can I use Doc View Java Maintenance 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-java-maintenance -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-java-maintenance, .gemini/skills/doc-view-java-maintenance, .github/skills/doc-view-java-maintenance and .opencode/skills/doc-view-java-maintenance in your project.
What does Doc View Java Maintenance need to run?
SKILL.md names no scripts, command-line tools or credentials: Doc View Java Maintenance is instructions for the agent only.
Does Doc View Java Maintenance 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 Java Maintenance 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 Java Maintenance use?
Doc View Java Maintenance 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 Java Maintenance use?
About 557 tokens (SKILL.md is roughly 2.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 Java Maintenance?
Skills that share tags, products or a category with Doc View Java Maintenance: Release Plugin (flutter/flutter-intellij, 2k stars), Amplicode Install (Amplicode/spring-skills, 126 stars), Idea MCP (dtprj/dongting, 208 stars) and Ij Debugger (xpinjection/test-driven-spring-boot, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Doc View Java Maintenance?
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.