feat: Add $skill-name autocomplete functionality

[roomote]

Implements $ autocomplete for Agent Skills in the chat textarea, similar to how / works for commands.

Features

UI/UX

• $ trigger works anywhere in message after whitespace/newline (not just at start)
• Fuzzy search filtering of skills by name
• Skills are mode-filtered (only shows skills available in current mode)
• Visual highlighting of valid $skill-name tokens in textarea
• Keyboard navigation (↑↓ arrows, Enter/Tab to select)

Backend

• requestSkills handler provides mode-filtered skill list to webview
• Send-time resolution: $skill-name tokens are detected and SKILL.md content is included in the prompt
• Structured metadata attached to skill selections for extension processing
• Supports both hyphenated and non-hyphenated skill names (e.g., $pdf-processing and $pdfprocessing)

Implementation Details

Frontend Changes

• Added Skill type to ContextMenuOptionType enum
• Extended shouldShowContextMenu() to detect $ trigger
• Added insertSkill() function for $skill-name insertion with trailing space
• Updated getContextMenuOptions() to handle $ queries with fuzzy matching
• Updated ChatTextArea to request and receive skills from extension
• Updated ContextMenu to render skill suggestions with descriptions
• Added skillRegexGlobal pattern for highlighting

Backend Changes

• Added Skill interface to ExtensionMessage and WebviewMessage types
• Added requestSkills message handler in webviewMessageHandler.ts
• Updated parseMentions() to detect and resolve $skill-name tokens
• Skills are loaded from SkillsManager and included as <skill> XML blocks
• Full SKILL.md content is injected into the prompt at send time

Tests

• Comprehensive tests for shouldShowContextMenu with $ trigger
• Tests for skill filtering and fuzzy matching
• Tests for insertSkill behavior
• Tests for skill resolution in parseMentions

Related

Implements the Slack discussion for skill autocomplete with:

• Insert $skill-name + trailing space
• Attach structured metadata for extension-side resolution
• Mode-filtered suggestions from SkillsManager

---

View task on Roo Code Cloud

[roomote]

Rooviewer   See task on Roo Cloud

Reviewed the $skill-name autocomplete implementation. Found 1 issue related to redundant file I/O and potential test mismatch.

Issues

• src/core/mentions/index.ts - Skill content is read twice from filesystem; tests may fail without fs mock

_{Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.}

[roomote]

This reads the skill content from the filesystem, but getSkillContent() already reads and parses the file (returning content in its instructions field). This creates two issues:

1. Redundant file I/O: The skill file is read twice - once in the validation loop via getSkillContent() and again here.

2. Test mismatch: The tests mock getSkillContent to return skill metadata with instructions, but this code ignores that and reads from the path directly. Since mocked paths like /path/to/skill/SKILL.md don't exist, fs.readFile throws and the tests would fail unless fs is globally mocked.

Consider storing the skill content during validation and reusing it here, or using the instructions field from SkillContent.

Suggested change

	try {
	// Read the full SKILL.md content
	const skillContent = await fs.readFile(skillInfo.path, "utf-8")
	parsedText += `\n\n<skill name="${skillName}">\n${skillContent}\n</skill>`
	} catch (error) {
	parsedText += `\n\n<skill name="${skillName}">\nError loading skill '${skillName}': ${error.message}\n</skill>`
	}
	// Use the skill content that was already fetched during validation
	const skillFullContent = await skillsManager.getSkillContent(skillName, currentMode)
	if (skillFullContent) {
	parsedText += `\n\n<skill name="${skillName}">\n${skillFullContent.instructions}\n</skill>`
	}

_{Fix it with Roo Code or mention @roomote and request a fix.}