القائمة
Zoom out from an unfamiliar code area and map how it fits into the bigger picture. Use when the user says to zoom out, go up a layer, map an area, or asks how code fits together.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use `uv` for Python workflows in this repo. Use when running Python scripts, adding dependencies, or replacing pip/python/venv commands.
Create a GitHub issue in the current repository with gh. Use when the user wants to capture work as an issue from Pi or through the /ghi command.
Synthesize current context into a structured PRD draft or publishable PRD artifact using a shared template. Use when the user wants a PRD from conversation context, a GitHub issue, or a saved draft path.
Interact with GitHub using the `gh` CLI. Use when working with GitHub issues, pull requests, workflow runs, or API queries.
Cache and refresh remote git repositories under ~/.cache/checkouts/<host>/<org>/<repo> so future references can reuse a local copy. Use this skill when the user points you to a remote git repository as reference or you encountered a remote git repo through other means.
Review upstream/reference sources against this repository and create GitHub checkpoint issues. Use when checking .pac/upstream-sources.yaml, tracking inspiration drift, or running /pac-upstream-checkpoints.
| name | pac-zoom-out |
| description | Zoom out from an unfamiliar code area and map how it fits into the bigger picture. Use when the user says to zoom out, go up a layer, map an area, or asks how code fits together. |
| license | MIT |
| compatibility | Pi coding agent |
| metadata | {"author":"mypac","stage":"shared"} |
Go up one layer of abstraction. Map the relevant modules and callers, using the project's domain vocabulary. Treat CONTEXT.md as the source of truth when present, and fall back to nearby docs or code names otherwise.
Resolve the area from the user's request or conversation. Read only the minimum context needed. Cover the area, big picture, modules, callers or entry points, flow, and useful next reads. Do not propose implementation changes unless the user asks.
