codespaces
Reduces onboarding time and refactoring risk by mapping code dependencies and impact paths automatically, enabling AI agents and developers to navigate compl…
Architecture-aware code search, dependency graphs, and impact analysis for Python, TypeScript, Rust, C#, Java, Go, Ruby, Rails, for AI coding agents.
- Find all functions calling a specific API endpoint to assess breaking change impact.
- Generate dependency graphs showing which modules depend on a deprecated library.
- Analyze code changes to identify affected services before deploying updates.
Reduces onboarding time and refactoring risk by mapping code dependencies and impact paths automatically, enabling AI agents and developers to navigate complex codebases without manual analysis.
AI coding agents and engineering teams managing large, multi-language monorepos requiring rapid impact assessment.
https://github.com/diskd-ai/codespaces
By diskd-ai
How to Get It
claude plugins install diskd-ai/codespaces
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Help me find all functions calling a specific API endpoint to assess breaking change impact
Trust Signals Auto-scanned
Community Pulse New
- GitHub Codespaces — Hacker News · 1769 pts
- GitHub’s engineering team has moved to Codespaces — Hacker News · 861 pts
- Codespaces but open-source, client-only, and unopinionated — Hacker News · 665 pts
3 mentions across 1 sources
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 52 GitHub stars; contributors unknown; last commit 0d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 52 GitHub stars; contributors unknown; last commit 0d ago; license MIT.