菜单
Use when an agent needs recent or historical change context: what changed recently, regressions, merged PRs, tickets, docs, incidents, deployments, releases, and source-history ingestion.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the task is centered on running, explaining, configuring, or troubleshooting the `potpie` command: doctor, login, pot management, source registration, search, graph workbench reads/writes, and pot scope behavior.
Use while debugging or troubleshooting failures, flaky tests, incidents, production alerts, CI failures, local dev setup issues, repeated bugs, prior fixes, failed attempts, and verification history.
Use when the task can read or write the project-memory graph through the potpie CLI: discover the contract with `graph catalog`, read named views with `graph read`, resolve entity identity with `graph search-entities`, create validated plans with `graph propose`, commit plans with `graph commit --verify`, inspect quality with `graph quality`, or capture uncertain work with `graph inbox`. Also covers writing retrieval-grade descriptions and responding to nudges. Prefer this over the MCP context_* tools whenever the shell is available.
Use for project infra and architecture context: environments, adapters, runtime configuration, deployments, service dependencies, datastores, API contracts, ownership, incidents, and dependency blast radius.
Use before writing, modifying, reviewing, refactoring, or testing code so repo/project preferences surface: error handling, file structure, frameworks, logging, dependency choices, testing, security, API style, and naming. Also use after code work when a reusable project preference should be recorded.
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.
| name | potpie-change-timeline |
| description | Use when an agent needs recent or historical change context: what changed recently, regressions, merged PRs, tickets, docs, incidents, deployments, releases, and source-history ingestion. |
Use this skill when the user asks what changed, when debugging a possible regression, or when ingesting source history from GitHub, Linear, Jira, docs, or deployment records.
Read the project timeline first. A pot is the project boundary and can contain multiple repos, so do not narrow to the current repo unless the user asks.
potpie graph read \
--subgraph recent_changes \
--view timeline \
--format table \
--time-window 7d \
--limit 20
Use the user's exact dates when provided:
potpie graph read \
--subgraph recent_changes \
--view timeline \
--format table \
--since 2026-06-01 \
--until 2026-06-15 \
--limit 50
Only narrow when the user gives a service, environment, or topic:
potpie graph read \
--subgraph recent_changes \
--view timeline \
--format table \
--scope service:<service-name> \
--query "<symptom feature deployment>" \
--time-window 14d \
--limit 20
Timeline context is correlation, not proof. Use it to choose files, PRs, tickets, or deploys to inspect, then verify the source ref before blaming a change. Timeline reads do not include uncommitted local work unless it was recorded.
For GitHub, Linear, Jira, docs, and similar sources, hydrate records with the agent's integration tools/connectors first. Do not use Potpie CLI queue ingestion as the source-history path.
Use the workbench write flow after reading the source:
potpie --json graph catalog --task "record timeline change"
potpie --json graph describe recent_changes --view timeline --examples
potpie --json graph propose --file mutation.json
potpie --json graph commit <plan_id> --verify
potpie --json graph history --plan <plan_id>
Use the source event time for occurred_at, not ingestion time. Add fixes,
decisions, bug patterns, or infra links only when the source explicitly supports
them.
Timeline capture is harness-led. Do not use scanner-driven graph updates or turn source titles into facts without reading the source.
Use this only when the potpie CLI is unavailable:
{"intent":"debugging","include":["timeline","prior_bugs","infra_topology"],"mode":"fast","source_policy":"references_only"}
Include families belong to the envelope surface (context_* MCP tools and
potpie resolve/potpie search); in the graph workbench they are served by the
graph views recent_changes.timeline, debugging.prior_occurrences, and
infra_topology.service_neighborhood — graph read does not accept include
family names.