1jehuang / 1jehuang/jcode

Proposal: configurable global skill paths

Open
#560 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

autonomous: no enhancement priority: medium triage: needs-decision
Dominant language
Rust
Stars
19.9k
Forks
2.3k
Avg merge
2d 7h
Merged PRs (30d)
30

Description

Heyy 🖤 Thx a lot for this amazing and inspiring project!

Since PRs are limited don't know whether you'd be offended to discuss it and for an issue to be opened instead

Jcode is already great out of the box with /skill and not impacted by Skill Token Context Problem,
so did a trial PR here https://github.com/Neved4/jcode/pull/1 that adds two small environment variables:

JCODE_SKILL_PATHS for the usual one-directory-deep layout
JCODE_SKILL_PATHS_RECURSIVE for recursively organized skill collections

Both work during startup and reload and should follow jcode existing skill perms and precedence logic
Recursive discovery should be bounded and deterministic, skip common noisy directories, avoid dir symlinks, and not scan duplicate paths twice, or that's the idea, but you know your codebase much better than we do! 🙈

Kept visibility and prompt out of scope, since that’s already being discussed in #141

Any feedback much appreciated,
Cheers, keep rocking!!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the skill discovery entry points used during startup and reload, then trace the existing /skill permission and precedence logic. The linked trial PR and this proposal describe the expected JCODE_SKILL_PATHS and JCODE_SKILL_PATHS_RECURSIVE behavior; done means both paths integrate with that logic while bounded recursive discovery remains deterministic and avoids duplicate or symlinked directories.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.