Remote repo, skills and nested folders creates empty tech-stack.md

[yusijs]

Description

We use monorepos, where we want to generate skills for certain packages. Our API is written in Java, and client code / libraries in node/typescript. When we generate the skill based on the entire repo, the tech-stack.md is practically blank:

# Tech Stack

## Configuration Files

- .gitignore

Using --ignore and --include does nothing to alleviate this, as it seems to only look for the dependency-files at the top-level directory.

Ideally I guess it should just look for all dependency files (i.e package.json, pom.xml etc) in the included files when creating the tech-stack.md file, or it should be possible to specify the dependency-file (i.e repomix --remote <url> --dependencies=path/to/package.json

Another solution would be #433 by specifying the path, as well as ignore/include, which would at least allow us to get the dependencies for the path we want to generate a skill for.

[github-actions]

Related Issues

I found some similar issues that might be helpful:

• Impossible to pack a remote with specific paths #433 - Impossible to pack a remote with specific paths - Directly related to this issue. Supporting specific subdirectory paths for remote repos would allow targeting a particular package within a monorepo, which would help the tech-stack detection find the correct dependency files.
• [Request] Non-interactive --skill-generate #1142 - [Request] Non-interactive --skill-generate - Related to the skill generation workflow. Non-interactive skill generation with parameter support could complement a solution here by allowing users to specify dependency file paths or target directories when generating skills.

These might provide additional context or solutions.

[yamadashy]

Hi, @yusijs!

Thanks for the detailed report!

I agree that ideally it should look for all dependency files in the included files, not just at the root level.

I'll look into fixing this.