profile-java-call-graph-toollisted
Install: claude install-skill HaroldHormaechea/project-builder
# Profile — Java Call-Graph Tool
Provisions `java-class-call-scanning` for the dev-team. The tool is a bytecode-level call-graph and diff-impact analyzer for Java projects (compiled `.class`, JARs, WARs). When this profile is active, the dev-team agents gain access to nine call-graph and diff-impact operations — either through MCP tools (preferred) or through bash CLI invocations against a cached jar (fallback).
Apply only when `PROJECT_BRIEF.md` → `## Profiles` lists `profile-java-call-graph-tool`.
## Precedence
`PROJECT_BRIEF.md` > this profile > model defaults. If the brief overrides any rule below, follow the brief and surface the conflict. If the brief is silent, this profile is authoritative.
## What the tool provides
Upstream: https://github.com/HaroldHormaechea/java-class-call-scanning
The same fat jar runs three ways:
1. **One-shot CLI** — `java -jar java-class-call-scanning.jar --compiled <paths> --diff <file> --export-format json` for a complete impact report on a Git diff.
2. **Daemon TCP CLI** — a long-lived process scoped to a project (classpath + sources); query subcommands talk to it over a loopback port.
3. **Daemon MCP stdio server** — the same daemon advertises its nine operations as MCP tools. Server identifies itself as `java-class-call-scanning`.
The nine operations:
| Operation | Purpose |
|------------------------|-------------------------------------