potpie-repo-baseline

name	potpie-repo-baseline
description	Use when establishing, refreshing, or deeply understanding a repository's baseline memory in Potpie: purpose, application type, features, services/modules, environments, deploy shape, dependencies, API contracts, datastores, integrations, ownership, and explicit preferences. The harness reads authored and code-adjacent sources, then writes graph workbench mutations.

Potpie Repo Baseline

Use this skill when the user asks to ingest, refresh, establish, or deeply understand what a repository is and how it works.

Procedure

1. Resolve the pot and source:

potpie --json pot info
potpie --json source list
potpie source add repo . --pot <pot-id-or-name>

Source registration records metadata only. It does not ingest or scan.

2. Discover the live graph contract:

potpie --json graph status
potpie --json graph catalog --task "deep repo baseline"
potpie --json graph describe features --view feature_context --examples
potpie --json graph describe infra_topology --view service_neighborhood --examples
potpie --json graph describe decisions --view preferences_for_scope --examples

3. Create todos for the baseline lanes: docs/product, repo map, runtime/deploy, API/data/integrations, preferences/workflows, synthesis, identity resolution, write, verify.
4. Read authored sources first, then inspect source files that are authoritative for durable facts: routes, service clients, adapters, deployment targets, API contracts, model/datastore usage, and test/workflow commands.
5. Resolve identity before writing:

potpie graph search-entities "<repo service feature>" --limit 10
potpie graph search-entities  -- Service --environment prod -- 10