CommandCodeAI / CommandCodeAI/command-code
Skill runner should be handled separately
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 4k
- Forks
- 350
- PR merge metrics
- No merged PRs in 30d
Description
Summary
Skill runner is very annoying, no access to ~/.commandcode/skills on the agent. Too many access requests.
Expected Behavior
Seamless skill runs managed by the harness and not by LLM.
Actual Behavior
For some reason it skill calls fall back to bash cat ...,
SHELL [echo "===== to-spec ====="; cat ~/.commandcode/skills/to-spec/SKILL.md; echo; ls ~/.commandcode/skills/to-spec/]
│ ===== to-spec =====
│ ---
│ name: to-spec
Steps to reproduce the issue
Call a skill in cmd from ~/.commandcode that calls other skills.
Command Code Version
1.38.2
Operating System
macOS
Terminal/IDE
VSCode
Shell
zsh
Session file (optional)
No response
Fix prompt (optional)
No response
Additional context
OS: macOS 27.0
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the nested skill call from cmd in ~/.commandcode and inspect where skill calls fall back to shell commands such as cat. Done means skills are handled by the harness, including nested calls, without repeated access requests or LLM-generated shell reads.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, zsh
- Domain
- ai, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100