AhuHub

安装方式

先执行 `ahuhub login` 绑定当前账号，再用 CLI 安装到本机 skill 目录。

CLI 安装命令

ahuhub install ide-vscode-release-packaging-f3a65c20

版本历史

2 versions

v0.2.0版本通过当前版本

上传：2026/06/07 22:07大小：4.1 KBSHA256 2ce0ab7c43a6

登录后下载

v0.1.0版本通过

上传：2026/06/07 00:58大小：2.5 KBSHA256 d7a9c670e5bb

登录后下载

校验结果

没有校验提示。

文件清单

3 files

路径	大小	SHA256
ide-vscode-release-packaging/.ahu-tool.json	392 B	156364648169fa46
ide-vscode-release-packaging/SKILL.md	3.3 KB	a385ac751ea32f44
ide-vscode-release-packaging/.ahu-tool_副本.json	392 B	156364648169fa46

SKILL.md

--- name: ide-vscode-release-packaging description: Use when packaging or publishing the ahu-tool JetBrains IDE plugin and VSCode extension together, collecting release artifacts into one versioned directory, validating packaged metadata, or deciding whether zip, vsix, and jar files should be kept together. --- # IDE / VSCode Release Packaging Use this skill for release packaging in `/Users/zhuanzmima0000/project.public/IDE-Plugin`. ## Version Rule - Do not change any version number unless the user explicitly asks for a target version. - If the user gives a target version, keep these in sync: - `ahu-tool/build.gradle.kts` - `ahu-tool/src/main/resources/META-INF/plugin.xml` - `ahu-tool-vscode/package.json` `version` - `ahu-tool-vscode/package.json` `scripts.package:vscode` - current release paths in docs when they mention the active release. ## Build Commands Build the VSCode extension from the host: ```bash cd /Users/zhuanzmima0000/project.public/IDE-Plugin/ahu-tool-vscode npm run package:vscode ``` Build the JetBrains IDE plugin inside the Java container: ```bash docker exec e3d961f469290a51108ba1e3b16c2c61e2df41aac400a40b0332b210304f7f6e bash -lc 'export JAVA_HOME=/usr/local/openjdk-21; export PATH=$JAVA_HOME/bin:/opt/gradle/bin:$PATH; cd /workspace/public/IDE-Plugin/ahu-tool && gradle clean packageIdeRelease --no-daemon --no-configuration-cache --console=plain' ``` ## Unified Release Directory After both builds pass, copy artifacts into: ```text /Users/zhuanzmima0000/project.public/IDE-Plugin/build/release/<version>/ ``` Expected files: ```text ahu-tool-<version>.zip ahu-tool-vscode-<version>.vsix ahu-tool-<version>.jar instrumented-ahu-tool-<version>.jar ``` It is OK to keep jar files in the same versioned release directory for archiving and troubleshooting. For Marketplace uploads, use: - JetBrains Marketplace: `ahu-tool-<version>.zip` - VSCode Marketplace: `ahu-tool-vscode-<version>.vsix` Do not upload the jar to JetBrains Marketplace unless there is a specific reason and the plugin has no dependency packaging requirement. The zip is the normal release artifact. ## Open VSX / Cursor Publishing Publish the VSCode extension to Open VSX when the user asks for Cursor marketplace availability. Cursor may take time to sync from Open VSX after publishing. Never write the Open VSX token to files, command history, docs, or final responses. Prefer reading it from stdin or an environment variable only for the current process. First-time namespace setup: ```bash npx ovsx create-namespace <publisher> -p "$OPEN_VSX_TOKEN" ``` Publish the packaged VSIX: ```bash npx ovsx publish /Users/zhuanzmima0000/project.public/IDE-Plugin/build/release/<version>/ahu-tool-vscode-<version>.vsix -p "$OPEN_VSX_TOKEN" ``` For this project, `<publisher>` comes from `ahu-tool-vscode/package.json` `publisher`. ## Verification Before final response: 1. Confirm `plugin.xml` parses with `xmllint --noout`. 2. Confirm the JetBrains packaged `META-INF/plugin.xml` has the requested version. 3. Confirm the VSIX `extension/package.json` has the requested version. 4. Confirm logo assets are present in both packages when icon changes are part of the release. 5. List the unified release directory contents. 6. If Open VSX publishing was requested, report whether namespace creation and publish succeeded, without printing the token.