Skip to content

Imported nested Claude Code skills lose their subtree scoping (no paths auto-population) #2556

Description

@dyoshikawa

Background

Finding from the PR #2555 review round. A skill imported from a nested apps/web/.claude/skills/deploy directory is scoped to that subtree by location in Claude Code, but toRulesyncSkill emits it identically to a root skill — the location information is dropped, and a later generate rewrites it to the root .claude/skills/ with global activation (leaving the nested original in place, so Claude Code then sees both under qualified names).

Solution / Next Steps

Auto-populate paths: ["apps/web/**"] (or the claudecode-specific frontmatter equivalent) from the discovered nested root during import, so the subtree scoping survives the round-trip. Needs the nested root to be plumbed from getConfiguredImportRoots through fromDir into toRulesyncSkill.

Metadata

Metadata

Assignees

No one assigned

    Labels

    maintainer-scrapRough notes for AI implementation. Not for human eyes.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions