core/go
8
0
Fork 0
generated from lthn/LEM
Code Issues 2 Pull requests 1 Projects Releases Packages Wiki Activity Actions
go/docs/cmd/dev/impact/index.md
Snider 9add6cf2ee refactor(cli): restructure cmd packages into subdirectories 
- Move CLI commands into subdirectories matching command hierarchy:
  dev/, go/, php/, build/, ci/, sdk/, pkg/, vm/, docs/, setup/, doctor/, test/, ai/
- Create shared/ package for common styles and utilities
- Add new `core ai` root command with claude subcommand
- Update package declarations and imports across all files
- Create commands.go entry points for each package
- Remove GUI-related files (moved to core-gui repo)

This makes the filesystem structure match the CLI command structure,
improving context capture and code organization.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-29 18:02:43 +00:00

1.2 KiB
Raw Permalink Blame History

core dev impact

Show impact of changing a repository.

Analyses the dependency graph to show which repos would be affected by changes to the specified repo.

Usage

core dev impact <repo-name> [flags]

Flags

Flag Description
--registry Path to repos.yaml (auto-detected if not specified)

Examples

# Show what depends on core-php
core dev impact core-php

# Show what depends on core-tenant
core dev impact core-tenant

Output

Impact of changes to core-php:

Direct dependents (5):
  core-tenant
  core-admin
  core-api
  core-mcp
  core-commerce

Indirect dependents (12):
  core-bio (via core-tenant)
  core-social (via core-tenant)
  core-analytics (via core-tenant)
  core-notify (via core-tenant)
  core-trust (via core-tenant)
  core-support (via core-tenant)
  core-content (via core-tenant)
  core-developer (via core-tenant)
  core-agentic (via core-mcp)
  ...

Total: 17 repos affected

Use Cases

  • Before making breaking changes, see what needs updating
  • Plan release order based on dependency graph
  • Understand the ripple effect of changes

See Also