cds-project-scan

Scan a repository to generate a CDS Compose YAML with x-cds-project and x-cds-env sections.

2|1|Updated Dec 10, 2025
One-click install
npx skills add https://github.com/inernoro/prd_agent --skill cds-project-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cds-project-scan
Source: https://github.com/inernoro/prd_agent/tree/main/.claude/skills/cds-project-scan
Command: npx skills add https://github.com/inernoro/prd_agent --skill cds-project-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scans a repository to automatically produce a CDS Compose YAML, removing manual assembly and configuration drift.

Core Features & Use Cases

  • Detects project structure, tech stacks, and environment settings across monorepos to infer deployable profiles.
  • Generates a CDS-compliant YAML with x-cds-project and x-cds-env sections ready for import into the CDS Dashboard.
  • Supports end-to-end workflow from discovery to YAML export, enabling one-click deployment across diverse stacks.

Quick Start

Run the skill at the repository root to generate a CDS YAML you can paste into the CDS Dashboard.

Frequently Asked Questions about cds-project-scan

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

FAQPage Schema
How do I generate a docker-compose YAML from a monorepo for deployment?

A repository scan analyzes multi-service project structures to infer tech stacks, infrastructure services, and environment variables. It outputs a standard docker-compose file with CDS extensions for quick import into the CDS Dashboard.

What is a CDS Compose YAML and when do I need it for multi-service projects?

A CDS Compose YAML is a standard docker-compose file augmented with x-cds-project and x-cds-env sections. You need it to import multi-service project configurations into the CDS Dashboard, removing manual assembly and configuration drift.

Can I automatically detect environment variables and routing prefixes for my tech stack?

Yes, scanning a repository automatically detects environment variables and routing prefixes across diverse tech stacks. It applies to multi-service projects and monorepos to infer deployable profiles and generate a CDS-compliant YAML.

How do I export a discovered project layout into a CDS-ready deploy format?

Run a scan at the repository root to discover services and generate a CDS-compliant YAML with x-cds-project and x-cds-env sections. You can then paste this exported file into the CDS Dashboard for deployment.

Does repository scanning work for infrastructure services across diverse stacks?

Repository scanning works across diverse stacks to infer infrastructure services and tech stacks. It supports an end-to-end workflow from discovery to YAML export for multi-service projects and monorepos.