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 defining or reviewing Doc View behavior contracts before changing PSI parsing, DTOs, Markdown output, uploads, exports, settings, UI-visible behavior, or IntelliJ…
Install Doc View Contract Design
$ npx skills add liuzhihang/doc-view --skill doc-view-contract-design -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install liuzhihang/doc-view doc-view-contract-design --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-contract-design .claude/skills/doc-view-contract-design && 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-contract-design" agent skill from https://github.com/liuzhihang/doc-view/tree/master/.codex/skills/doc-view-contract-design into .claude/skills/doc-view-contract-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-view-contract-design", 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-contract-designType 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-contract-design -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install liuzhihang/doc-view doc-view-contract-design --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-contract-design .agents/skills/doc-view-contract-design && 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-contract-design" agent skill from https://github.com/liuzhihang/doc-view/tree/master/.codex/skills/doc-view-contract-design into .agents/skills/doc-view-contract-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-view-contract-design", 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-contract-design -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install liuzhihang/doc-view doc-view-contract-design --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-contract-design .cursor/skills/doc-view-contract-design && 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-contract-design" agent skill from https://github.com/liuzhihang/doc-view/tree/master/.codex/skills/doc-view-contract-design into .cursor/skills/doc-view-contract-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-view-contract-design", 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-contract-design--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-contract-design -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install liuzhihang/doc-view doc-view-contract-design --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-contract-design .gemini/skills/doc-view-contract-design && 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-contract-design" agent skill from https://github.com/liuzhihang/doc-view/tree/master/.codex/skills/doc-view-contract-design into .gemini/skills/doc-view-contract-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-view-contract-design", 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-contract-designInstalls 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-contract-design -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-contract-design .github/skills/doc-view-contract-design && 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-contract-design" agent skill from https://github.com/liuzhihang/doc-view/tree/master/.codex/skills/doc-view-contract-design into .github/skills/doc-view-contract-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-view-contract-design", 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-contract-design -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-contract-design --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-contract-design .opencode/skills/doc-view-contract-design && 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-contract-design" agent skill from https://github.com/liuzhihang/doc-view/tree/master/.codex/skills/doc-view-contract-design into .opencode/skills/doc-view-contract-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-view-contract-design", 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-contract-design- GitHub stars
- 207
- Token cost
- ~539 tokens
- SKILL.md length
- 226 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
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…
- Works in 7 steps: Identify the observable area:… → Confirm an apply-ready OpenSpec change… → Define… → …
- Reviewing Doc View behavior contracts before changing PSI parsing
- 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 Contract Design is an agent skill from liuzhihang/doc-view. Use when defining or reviewing Doc View behavior contracts before changing PSI parsing, DTOs, Markdown output, uploads, exports, settings, UI-visible behavior, or IntelliJ compatibility.
Its SKILL.md is about 540 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 Documents & Office. It works with JetBrains IDEs and Java. The repository describes itself as: IDEA 插件 Doc View 的仓库地址. The licence is MIT.
When your agent uses it
- Reviewing Doc View behavior contracts before changing PSI parsing
- Markdown output
- UI-visible behavior
- IntelliJ compatibility
Example prompts
- “/doc-view-contract-design”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Identify the observable area: Spring/Feign/Dubbo PSI, DTO, Markdown, export, upload, settings, UI, performance, or compatibility.
- Confirm an apply-ready OpenSpec change exists for behavior work; write normative requirements to its specs/, not docs/contracts/.
- Define Java/settings/platform/external-service inputs and assumptions.
- Define expected DocView/Body/Param/Header, Markdown, payload, UI, notification, or compatibility outputs.
- Define unsupported, fallback, sensitive-data, and explicitly unchanged cases.
- Choose direct validation: PSI fixture, DTO assertion, golden Markdown, payload check, runIde, or Plugin Verifier.
- Review recursion, user-template, IntelliJ lifecycle, EDT, and secret-handling risks.
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 Contract Design loads about 539 tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 226 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). 226 words, ~539 tokens.
Download SKILL.mdSave it as
.claude/skills/doc-view-contract-design/SKILL.md (or your agent's skills folder).- name
- doc-view-contract-design
- description
- Use when defining or reviewing Doc View behavior contracts before changing PSI parsing, DTOs, Markdown output, uploads, exports, settings, UI-visible behavior, or IntelliJ compatibility.
Doc View Contract Design
Use this skill before implementation work that changes user-visible or integration-visible behavior. OpenSpec owns proposal/design/spec/tasks; this skill supplies Doc View domain checks.
Read First
AGENTS.mddocs/contract-design.md- The active change status and every
contextFilespath returned byopenspec instructions apply --change <name> --json docs/architecture.mdwhen package, service, DTO, settings, extension, or data flow boundaries are involveddocs/performance-guide.mdwhen PSI, UI, rendering, export, upload, recursion, or cache performance can changedocs/intellij-compatibility.mdwhen IntelliJ API, Gradle platform, descriptor, extension, or compatibility behavior is involved
Steps
- Identify the observable area: Spring/Feign/Dubbo PSI, DTO, Markdown, export, upload, settings, UI, performance, or compatibility.
- Confirm an apply-ready OpenSpec change exists for behavior work; write normative requirements to its
specs/**, notdocs/contracts/**. - Define Java/settings/platform/external-service inputs and assumptions.
- Define expected
DocView/Body/Param/Header, Markdown, payload, UI, notification, or compatibility outputs. - Define unsupported, fallback, sensitive-data, and explicitly unchanged cases.
- Choose direct validation: PSI fixture, DTO assertion, golden Markdown, payload check,
runIde, or Plugin Verifier. - Review recursion, user-template, IntelliJ lifecycle, EDT, and secret-handling risks.
Guardrails
- Do not change Java while only designing the contract.
- Do not create a parallel contract under
docs/contracts/**; OpenSpec specs are normative. - Do not include real tokens, production URLs, or private user code in artifacts or fixtures.
- Do not make implementation details normative unless users or integrations observe them.
- Keep later production implementation Java-only.
© 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-contract-design of liuzhihang/doc-view.
Open the folder on GitHubat commit 00f1f94
Compare with similar skills
Doc View Contract Design 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 Contract Design this skillliuzhihang/doc-view | 207 | — | ~539 | Automated safety check: Pass | MIT | |
| Release Pluginflutter/flutter-intellij | 2k | — | ~1k | Automated safety check: Pass | BSD-3-Clause | |
| Code StyleJetBrains/intellij-community | 21k | — | ~795 | Automated safety check: Pass | Custom licence | |
| Jugg Android Dev Loopniki914/zafiro | 235 | — | ~2k | Automated safety check: Pass | MIT | |
| Amplicode InstallAmplicode/spring-skills | 128 | — | ~2.6k | Automated safety check: Pass | None | |
| Idea MCPdtprj/dongting | 208 | — | ~698 | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Code Style
JetBrains/intellij-community
Apply IntelliJ Kotlin and Java code style when writing or reviewing.
Jugg Android Dev Loop
niki914/zafiro
A skill your agent uses when editing source files (Java/Kotlin/XML/layout/AndroidManifest/Gradle) in a Android project, or when user asks to build/deploy/verify an Android app.
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.
More from liuzhihang/doc-view
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 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.
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
Categories
Questions about Doc View Contract Design
What does Doc View Contract Design do?
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 Contract Design is an agent skill from liuzhihang/doc-view. Use when defining or reviewing Doc View behavior contracts before changing PSI parsing, DTOs, Markdown output, uploads, exports, settings, UI-visible behavior, or IntelliJ compatibility.
When should I use Doc View Contract Design?
Doc View Contract Design fits situations like: reviewing Doc View behavior contracts before changing PSI parsing; markdown output; UI-visible behavior; intelliJ compatibility.
How do I install Doc View Contract Design in Claude Code?
Run `npx skills add liuzhihang/doc-view --skill doc-view-contract-design -a claude-code`. Or copy the skill folder (.codex/skills/doc-view-contract-design in liuzhihang/doc-view) into .claude/skills/doc-view-contract-design in your project. Claude Code loads it when a task matches its description.
How do I install Doc View Contract Design in Codex?
Run `npx skills add liuzhihang/doc-view --skill doc-view-contract-design -a codex`. Or copy the skill folder (.codex/skills/doc-view-contract-design in liuzhihang/doc-view) into .agents/skills/doc-view-contract-design in your project. Codex loads it when a task matches its description.
Can I use Doc View Contract Design 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-contract-design -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-contract-design, .gemini/skills/doc-view-contract-design, .github/skills/doc-view-contract-design and .opencode/skills/doc-view-contract-design in your project.
What does Doc View Contract Design need to run?
SKILL.md names no scripts, command-line tools or credentials: Doc View Contract Design is instructions for the agent only.
Does Doc View Contract Design 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 Contract Design 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 Contract Design use?
Doc View Contract Design 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 Contract Design use?
About 539 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 Contract Design?
Skills that share tags, products or a category with Doc View Contract Design: Release Plugin (flutter/flutter-intellij, 2k stars), Code Style (JetBrains/intellij-community, 21k stars), Jugg Android Dev Loop (niki914/zafiro, 235 stars) and Amplicode Install (Amplicode/spring-skills, 128 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Doc View Contract Design?
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.