القائمة
Guidelines for versioning, packaging, and releasing the ManulAI VS Code extension. Covers version bumps, VSIX builds, documentation sync, and release checks.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Guidelines for modifying the VS Code Chat participant (@manulai) in src/copilotChatParticipant.ts. Covers streaming, slash commands, auto-approve state, agent mode awareness, history handling, and keeping it independent from legacy code.
Guidelines for modifying the workspace agent instructions reader in src/agentInstructionsReader.ts. Covers file discovery, AGENTS.md/CLAUDE.md parsing, and injection into the Copilot Chat system prompt.
Guidelines for modifying Ollama streaming and reasoning extraction in src/ollamaStreamParser.ts. Covers NDJSON parsing, <think> tag extraction, and integration with the Copilot Chat participant.
Guidelines for modifying the ManulAI Settings webview panel in src/settingsPanel.ts. Covers Activity Bar registration, model fetching from Ollama, webview HTML, message passing, and VS Code settings updates.
Guidelines for modifying the workspace skills reader in src/skillsReader.ts. Covers skill discovery, frontmatter parsing, and injection into the Copilot Chat system prompt.
Atomically bump the ManulAI extension version across all 6 required locations (package.json, package-lock.json ×2 occurrences, README.md What's New, README-dev.md Release Notes, CLAUDE.md, .github/copilot-instructions.md) and verify the build still compiles. Enforces the CLAUDE.md rule that packaging version changes update every one of these files in the same change.
| name | extension-packaging |
| description | Guidelines for versioning, packaging, and releasing the ManulAI VS Code extension. Covers version bumps, VSIX builds, documentation sync, and release checks. |
This skill governs how ManulAI is versioned, packaged, and released as a .vsix file.
package.json — version, engine requirements, contributions.package-lock.json — lockfile version parity.README.md — user-facing changelog (## What's New).README-dev.md — developer release notes (## Release Notes).CLAUDE.md — version header..github/copilot-instructions.md — must stay byte-identical to CLAUDE.md.AGENTS.md — version and feature sync.package.jsonpackage-lock.json (two occurrences: top-level + packages."")README.md (## What's New first bullet)README-dev.md (## Release Notes first bullet)CLAUDE.md (Version: X at top).github/copilot-instructions.md (identical to CLAUDE.md)AGENTS.md (if version or features changed)npm run compile before editing version strings. If the build is broken, abort the bump.npm run compile after all edits to confirm nothing regressed.diff CLAUDE.md .github/copilot-instructions.md must produce no output. These files are kept byte-identical intentionally.npx vsce package --no-yarn to produce the .vsix. The prepublish script runs npm run compile automatically.# 1. Confirm current version is consistent
grep -n "0.0.X" package.json package-lock.json README.md README-dev.md CLAUDE.md .github/copilot-instructions.md
# 2. Build must pass
npm run compile
# 3. Edit all 6+ files with the new version
# 4. Build again
npm run compile
# 5. Verify CLAUDE.md parity
diff CLAUDE.md .github/copilot-instructions.md
# 6. Re-verify version grep
grep -n "0.0.Y" package.json package-lock.json README.md README-dev.md CLAUDE.md .github/copilot-instructions.md
# 7. Package
npx vsce package --no-yarn
package-lock.json has TWO version occurrences.CLAUDE.md but not .github/copilot-instructions.md.README.md (user-facing): one paragraph, technical tone, alpha-stage. Describe the mechanism of the fix, not just the symptom.
README-dev.md (developer): same first-line plus structured sub-bullets naming files, functions, and mechanisms.
Do NOT write vague marketing text like "Improved reliability" or "Various bug fixes".