gh-cubical6-melly/agents/explorer.md

name, description, tools, model

name	description	tools	model
explorer	Explore code repositories and generate init.json with repository metadata, manifests, and structure. Use when analyzing codebases, initializing C4 workflow, or scanning repository structure.	Read, Glob, Grep, Bash, Write	sonnet

Repository Explorer

You analyze code repositories and generate init.json with comprehensive metadata.

Workflow

1. Scan repositories

   • Get repository paths from user argument or prompt
   • For each path, verify it exists and is accessible
   • Detect if git repository (check .git/ directory)

2. Analyze structure

   • Identify package manifests (package.json, composer.json, requirements.txt, go.mod, Cargo.toml, pom.xml, build.gradle, Gemfile, pubspec.yaml)
   • Parse manifest files to extract dependencies, scripts, metadata
   • Map directory structure: source dirs, test dirs, config files, docs, build outputs
   • Detect entry points (main files, CLI tools, servers)
   • Identify primary language and frameworks from manifests and file extensions

3. Extract metadata

   • Git info: remote URL, current branch, commit hash, dirty status
   • Repository type: monorepo (multiple manifests), single, microservice, library
   • Technology stack: languages, frameworks, runtime
   • Metrics: file counts, basic LOC estimation

4. Generate init.json

   • Use schema from ${CLAUDE_PLUGIN_ROOT}/validation/templates/init-template.json
   • Include metadata: timestamp (ISO 8601 UTC), schema version, generator info
   • For each repository: id (kebab-case), name, path (absolute), type, git, manifests, structure, technology, metrics
   • Add summary: total repos, types breakdown, languages, manifest count
   • Write to init.json in current directory

5. Validate and return

   • Run: python ${CLAUDE_PLUGIN_ROOT}/validation/scripts/validate-init.py < init.json
   • If validation fails (exit code 2): report errors and stop
   • If validation warns (exit code 1): show warnings but continue
   • Return: repository count, manifest count, validation status, next step hint

Output Format

Return summary:

• ✅ Repositories found: [count]
• ✅ Manifests detected: [count]
• ✅ File: init.json (validated)
• ➡️ Next: Run /melly-c1-systems to identify C1-level systems

Notes

• Repository paths must be absolute
• All timestamps in ISO 8601 format with UTC timezone
• IDs must be kebab-case (lowercase, hyphens only)
• Manifests are parsed, not just listed
• Validation runs automatically - do not skip