LaunchKit · 2026
Back to Skills

document-multiple-repository

Gera documentação técnica consolidada para sistemas de software com múltiplos repositórios (frontend, backend.

0
742 downloads
by @dannyxyz22

Setup & Installation

openclaw skills install @dannyxyz22/document-multiple-repository

Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:

npx clawhub install document-multiple-repository

What This Skill Does

Generates consolidated technical documentation for software systems spread across multiple repositories, including frontends, backends, microservices, and wikis stored locally. It discovers git repos, clusters them into logical systems, and produces structured markdown docs covering architecture, APIs, deployment, and processes.

Instead of manually piecing together docs from each repo, the skill scans and clusters all repos at once and outputs a consistent documentation structure in a single pass.

When to use it

  • Documenting a microservices platform cloned from multiple GitHub repos
  • Creating an architecture overview before onboarding a new engineer
  • Mapping all repos in a monorepo-adjacent folder structure
  • Extracting deployment steps from scattered wikis and manifests
  • Generating API docs from routes across frontend and backend repos

Example Workflow

Here's how your AI assistant might use this skill in practice.

INPUT

User asks: Run skill document-multiple-repository on /projects/my-platform

AGENT
  1. 1Scans ROOT_PATH recursively to detect all .git directories and wiki repos
  2. 2Groups repos by filesystem proximity into logical systems
  3. 3Analyzes each repo for language, framework, service type, API routes, and wiki content
  4. 4Generates system-level docs (SYSTEM_OVERVIEW.md, ARCHITECTURE.md, REPOSITORY_MAP.md, DEPLOYMENT.md)
  5. 5Generates per-repo docs (README.generated.md, API.generated.md, CODE_STRUCTURE.md)
OUTPUT

A structured documentation tree under OUTPUT_PATH with one folder per system, containing consolidated markdown files for architecture, APIs, deployment, and processes