القائمة
Map an unfamiliar code repository into a structured manifest — languages, entry points, build/test commands, and a one-line purpose for each top-level directory. Use when asked to "explore", "map", "summarize the structure of", or "get oriented in" a repo/workspace.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
How to connect to and authenticate with external services (APIs) from inside this sandbox. Read this whenever a task needs an authenticated external service — a code host, an issue tracker, a cloud API, etc. It explains how authentication works here (the sandbox injects credentials for you), how to initiate a connection, and exactly what to expect — including what to do when access is denied.
Produce a structured inventory of the current workspace — file counts and total size by extension, the largest and most-recently-modified files, and the top-level layout. Use when asked to "summarize", "inventory", "take stock of", "what's in", or "give an overview of" the workspace (works for any folder, not just code repos).
| name | repo-explorer |
| description | Map an unfamiliar code repository into a structured manifest — languages, entry points, build/test commands, and a one-line purpose for each top-level directory. Use when asked to "explore", "map", "summarize the structure of", or "get oriented in" a repo/workspace. |
Turn an unfamiliar repository into a deterministic, structured manifest. Follow these steps in order, then emit the JSON exactly as specified.
List the tree. Run Bash: ls at the workspace root, then Glob **/* (cap depth ~3). Ignore node_modules, target, .git, bin, obj, dist, and .venv. Note the top-level directories.
Detect languages & manifests. Look for package.json (JS/TS), *.csproj/*.sln (C#), Cargo.toml (Rust), pyproject.toml/requirements.txt (Python), go.mod (Go), pom.xml/build.gradle (JVM). Each manifest implies a language and a toolchain.
Find entry points & commands. Locate Program.cs, main.rs, index.ts/index.js, __main__.py/main.py, cmd/*/main.go, etc. Derive the build + test commands from the manifests (e.g. dotnet build/dotnet test, npm run build/npm test, cargo build/cargo test, pytest, go build/go test ./...).
Confirm purpose. Read the top-level README* (if present) and the primary manifest(s) to confirm what the project does and to label each top-level directory.
Emit the manifest. Output one fenced ```json block matching this exact schema (no extra keys):
{
"languages": ["..."],
"entryPoints": ["..."],
"build": ["..."],
"test": ["..."],
"topLevelDirs": [{ "path": "...", "purpose": "..." }],
"summary": "one-paragraph overview"
}
Notes: Always Read a file before editing it, and keep every command read-only (list/read/inspect only) during exploration — do not build, install, or modify anything.