Which Pharaoh tool answers which structural question about a mapped repo (TypeScript, JavaScript, Python): where code lives, what calls it, what a change affects, what a module contains and what nothing runs. Use when Pharaoh's tools are connected and the question is about the structure of a repo Pharaoh maps.
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Pharaoh?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/pharaoh-so-pharaoh-a0414d1c)
---
name: pharaoh
description: "Which Pharaoh tool answers which structural question about a mapped repo (TypeScript, JavaScript, Python): where code lives, what calls it, what a change affects, what a module contains and what nothing runs. Use when Pharaoh's tools are connected and the question is about the structure of a repo Pharaoh maps."
---
# Pharaoh Tool Guide
Pharaoh maps codebases into queryable knowledge graphs — functions, dependencies, modules, connections. No source code stored.
## Pick the tool by the question
| Question | Tool |
|---|---|
| Does X already exist? Where is Y implemented? | `search_functions` |
| What calls X? What breaks if I change it? Which endpoints or cron jobs reach it? | `get_blast_radius` |
| What's in this module, what does it depend on, who calls into it? | `get_module_context` |
| Is this code dead or wired in? What can I delete? | `get_unused_code` |
| How is the repo laid out? Which module owns this? What's the repo called? | `get_codebase_map` |
| Several of these at once (planning a change, reviewing a PR) | `pharaoh_recon` |
The graph reflects the default branch at its last mapped push, and a response says when a newer push is still being mapped. Grep and file reads cover what it leaves out: code that isn't on the default branch yet (other branches, uncommitted edits), literal text (strings, error messages, config values, comments, non-code files) and renames, which change every reference, tests and mocks included.
## Repos that aren't mapped
Repos are mapped through the Pharaoh GitHub App, installed on the account or org that owns them. Every repo is mapped during the trial and on Pro, and mapped repos re-map on every push; after the trial, get_codebase_map keeps answering. `pharaoh_account` shows each workspace's plan and, where the App isn't installed, its install link. `search_functions` accepts any of the user's mapped repo names.
## Workflows
**PR review:** `pharaoh_recon` (map + touched modules + blast radius) → `get_blast_radius` on the riskiest changed functions. Verdict: SHIP, SHIP WITH CHANGES, or BLOCK.
## Utilities
- `pharaoh_account` — plan and mapped repos in each workspace
- `pharaoh_manage_repo` — re-map a repo now
Full docs at [pharaoh.so/docs](https://pharaoh.so/docs).
## Connection
The plugin registers the Pharaoh connector. To connect it and sign in with GitHub:
- **Claude Code:** run `/mcp` and select `plugin:pharaoh:pharaoh`.
- **claude.ai and Cowork:** open Pharaoh in Customize > Plugins and use its Connectors tab.