doc-view-java-maintenance

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

Ir para a instalação

Repositório: liuzhihang/doc-view
Última atividade na origem: 11 de julho de 2026 às 14:02
Idioma detectado do SKILL.md: inglês
Estrelas: 207
Forks: 53

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/liuzhihang/doc-view --skill doc-view-java-maintenance

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

doc-view-contract-design

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.

2026-07-11

doc-view-docs-maintenance

Use when creating or updating Doc View repository documentation, AGENTS.md, AI workflow guidance, OpenSpec configuration, or repo-local Codex skills.

2026-07-11

doc-view-release-readiness

Use when preparing, checking, or reviewing a Doc View plugin release, including changelog, version, plugin verification, manual IDE validation, Marketplace preparation, and rollback notes.

2026-07-11

Ver todas deste repositório

Doc View Java Maintenance

Use this skill for production plugin work after an observable behavior contract is apply-ready.

Read First

AGENTS.md

docs/architecture.md

Every active apply contextFiles path returned by OpenSpec; runtime work requires proposal/design/spec/tasks context

docs/contract-design.md for PSI, DTO, Markdown, upload, export, settings, writeback, or UI behavior

docs/performance-guide.md for PSI, recursion, cache, background task, rendering, export, upload, or UI responsiveness

docs/intellij-compatibility.md for 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, 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 project disposal.

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.

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.