Menú
Map project architecture: discover modules, build call graphs, visualize structure, trace critical paths. Complete architecture overview with dependency flows.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Analyze code structure: parse functions, classes, imports, and complexity metrics. Use to understand a file or project without reading the source code directly.
Extract a specific function, class, or method from a file using Code Scalpel. Use when you need to show a symbol without reading the entire file—saves 95% of context.
Verify code compliance with policies and standards: HIPAA, SOC2, PCI-DSS, custom style guides. Validate policy file integrity with cryptographic verification.
Safe refactoring workflow: find all usages, trace dependencies, simulate changes, generate baseline tests, then apply with backup. Behavior-preserving refactor.
Full security audit: detect local vulnerabilities, cross-file taint flows, CVEs in dependencies, and polyglot sink patterns. Complete security scan pipeline.
Install and verify the Code Scalpel MCP server. Checks if codescalpel is already installed in Claude Code, runs `claude mcp add` if needed, and confirms connection by fetching capabilities.
| name | cs-map |
| description | Map project architecture: discover modules, build call graphs, visualize structure, trace critical paths. Complete architecture overview with dependency flows. |
| allowed-tools | ["mcp__codescalpel__crawl_project","mcp__codescalpel__get_call_graph","mcp__codescalpel__get_project_map","mcp__codescalpel__get_cross_file_dependencies"] |
| preamble-tier | 1 |
Discover your entire project structure: modules, call graphs, dependencies, and complexity hotspots. Visualize how everything connects.
/cs-map
/cs-map src/
/cs-map src/api/
Discover all modules and files:
Map function-to-function calls:
High-level project map:
For important symbols:
Project Structure
Dependency Flow
Complexity Hotspots
Call Patterns
Project Structure:
├── src/
│ ├── api/ (HTTP handlers, 12 functions)
│ │ ├── users.py
│ │ └── products.py
│ ├── services/ (business logic, 34 functions)
│ │ ├── auth.py
│ │ ├── payment.py
│ │ └── notifications.py
│ ├── models/ (data models, 8 classes)
│ ├── utils/ (helpers, 15 functions)
│ └── main.py (entry point)
Call Graph (from main):
main()
├─→ setup_api()
│ └─→ register_routes()
│ ├─→ api.users.list_users()
│ └─→ api.products.get_product()
└─→ run_server()
Complexity Hotspots:
1. services/payment.py — process_payment() [CC: 8]
2. api/users.py — validate_request() [CC: 7]
3. models/user.py — User.save() [CC: 6]
✅ Onboarding to a new codebase ✅ Planning a major refactor ✅ Understanding system boundaries ✅ Finding where to add features ✅ Identifying technical debt ✅ Documenting architecture ✅ Preparing for code review
/cs-extract — Dive into specific functions/cs-analyze — Understand a module/cs-refactor — Improve the structure/cs-security — Check for vulnerabilitiesSee CLAUDE.md for the complete architecture mapping workflow.