skill suggest fails to detect technologies in multi-project repositories that are not monorepos

[yacosta738]

skill suggest is not detecting any technologies when executed from the repository root in repositories containing multiple independent projects inside subdirectories.

This is not a monorepo in the traditional sense:

• there is no workspace configuration
• no root package.json
• no root build system
• no shared dependency management

The repository simply contains multiple standalone projects grouped in the same git repository.

However, skill suggest currently returns:

➤ Detected technologies
none
➤ Recommended skills
none
➤ Summary
Detected: 0
Recommended: 0
Installable: 0

even though the repository clearly contains detectable technologies.

⸻

Repository Structure (sanitized)

.
├── project-alpha
│   ├── pom.xml
│   ├── Dockerfile
│   ├── src/
│   │   ├── main/java/
│   │   └── resources/
│   ├── docs/
│   └── scripts/
│
├── project-beta
│   ├── pom.xml
│   ├── Dockerfile
│   ├── src/
│   │   ├── main/java/
│   │   └── resources/
│   ├── docs/
│   └── scripts/
│
└── tmp/
    └── misc-files/

⸻

Expected Behavior

skill suggest should:

• recursively scan subdirectories
• detect technologies inside nested standalone projects
• recommend skills based on detected tech stacks

For example, in this repository it should at least detect:

• Java
• Maven
• Docker
• Spring Boot (from project structure / dependencies)

⸻

Current Behavior

Detection only appears to work when:

• running the command inside each individual project directory

Running from the git root returns no detections.

⸻

Reproduction

cd repo-root
pnpm dlx @dallay/agentsync skill suggest

Output:

➤ Detected technologies
  none

⸻

Possible Root Cause

The detection logic may currently assume:

• a single-project repository
• or a formal monorepo layout

and may stop scanning if no recognizable tech markers exist at the repository root.

⸻

Suggested Improvement

Possible approaches:

1. Recursive project discovery
   • scan nested directories for known manifests
   • e.g. pom.xml, package.json, build.gradle, Cargo.toml, etc.
2. Multi-project aggregation
   • merge detections across discovered projects
3. Better repository classification
   • distinguish between:
     • monorepos
     • multi-project repositories
     • single-project repositories

⸻

Additional Context

This pattern is relatively common in enterprise/internal repositories where:

• multiple migration projects
• integration services
• or standalone deployables

are grouped under the same git repository without using a formal monorepo toolchain.

[linear]

DALLAY-365