subprojects

Enumerate repository sub-folders and output scannable sub-paths to report.json.

Updated May 20, 2026
One-click install
npx skills add https://github.com/lukehinds/scrutineer-attest-test --skill subprojects
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subprojects
Source: https://github.com/lukehinds/scrutineer-attest-test/tree/main/skills/subprojects
Command: npx skills add https://github.com/lukehinds/scrutineer-attest-test --skill subprojects

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enumerates scannable sub-folders inside a repository so analysts can scope deep-dive scans to specific sub-paths instead of treating the entire tree as a single unit.

Core Features & Use Cases

  • Detects explicit or inferred sub-projects by scanning manifest cues and folder structures within a reasonable depth.
  • Helps teams segment large monorepos into discrete, independently scannable units to optimize security analysis.
  • Provides deterministic enumeration results suitable for repo overviews and reproducible scoping.

Quick Start

Enumerate all sub-folders under the repository root and surface them in report.json for targeted scoping.

Frequently Asked Questions about subprojects

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify scannable sub-folders in a monorepo for targeted security scans?

Sub-project enumeration detects explicit or inferred scannable folders by analyzing manifest cues and folder structures within a reasonable depth, segmenting large monorepos into discrete units for targeted analysis.

How do I scope a deep-dive security scan to specific sub-paths instead of the entire repository tree?

Sub-project enumeration produces a deterministic JSON report file at report.json, listing all identified sub-paths within the repository suitable for reproducible scoping and targeted analysis.

Can I use sub-project enumeration to segment large monorepos with multiple modules?

Sub-project enumeration uses manifest cues and structural depth analysis to detect inferred sub-projects, distinguishing discrete scannable units within a repository rather than treating the entire tree as a single unit.

What is the best way to generate a reproducible scoping report for repository sub-projects?

Sub-project enumeration provides deterministic results by analyzing repository manifests and folder structures, ensuring reproducible scoping for security scans without treating the entire tree as a single unit.

Why does repository scanning treat my entire monorepo as a single unit instead of individual modules?

Yes, sub-project enumeration detects explicit or inferred sub-projects by scanning manifest cues and folder structures within a reasonable depth, segmenting large monorepos with multiple modules into discrete scannable units.