[Issue]: HVE-Core VS Code Extension Scripts Not Accessible to Agent Reasoning #390
Description
Issue Description
Issue Description
When using the HVE-Core VS Code Extension on a new project, agent reasoning encounters errors for missing scripts or instructions files that the agent cannot find. These are referenced in workflows with the agents but not accessible locally due to installation mode. This impacts the extension's ability to fulfill certain automation tasks that rely on helper scripts, as well as the GHCP agent being able to load instructions dynamically.
Observable Behavior
The agent attempts to locate scripts that exist in the HVE-Core repository but are not bundled with or accessible to the VS Code extension installation:
"The pr-ref-gen.sh script doesn't exist in this repo. I need to use the GitHub MCP tools to get the PR information. Let me search for the GitHub MCP tools."
This occurs because:
- Extension Installation: When HVE-Core is installed as a VS Code extension, only the extension package contents are available locally
- Missing Script Bundle: Helper scripts from the repository (such as
pr-ref-gen.shand others) are not packaged with the extension > UPDATE: this is not the issue, the scripts are packaged but path resolution is the issue. - Reasoning Impact: The agent recognizes script references in workflows but cannot access them, leading to fallback behaviors or incomplete functionality
Installation Method Comparison
| Installation Method | Script Availability | User Experience |
|---|---|---|
| Git submodule | ✅ Available | Scripts accessible, full functionality |
| Peer clone | ✅ Available | Scripts accessible, full functionality |
| VS Code extension | ❌ Not available | Scripts missing, limited functionality |
Expected Behavior
When using the HVE-Core extension, the agent should have access to all necessary scripts and utilities required for automated workflows without requiring manual repository cloning or submodule setup.
Current Workarounds
Short-term
- Use Git submodule or peer clone installation methods when script access is required
- Remove references to unavailable scripts from workflows
- Implement MCP tool alternatives where applicable (e.g., GitHub MCP tools for PR information)
Long-term (In Evaluation)
- SKILLS Migration: Evaluate moving helper scripts into SKILLS framework
- Benefit: Scripts would be packaged with the extension
- Blocker: SKILLS packaging capability is in development and not yet available
- Script Bundling: Package essential scripts directly with the extension
- Reference Cleanup: Remove or update script references that are not universally available
Impact
- Severity: Medium - Extension remains functional but with reduced capabilities
- Frequency: Occurs consistently when using extension installation method
- Scope: Affects any workflow that references repository scripts (PR generation, automation utilities, etc.)
Additional Context
This issue highlights a gap between the repository-based development experience and the extension-based user experience. The extension provides easier setup but loses access to the supporting script ecosystem.
Related Considerations
- Extension users expect a self-contained, zero-setup experience
- Repository scripts assume full repository access
- Migration to SKILLS would align with extension packaging model
- Interim solution needed until SKILLS packaging is available
Additional Context
No response