Potpie Change Timeline

DevOps & Security

potpie-change-timeline

Potpie Change Timeline is an Agent Skill for devops & security published in the potpie-ai/potpie repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

View on GitHub ↗

QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

Open your project in Codex.
Copy and paste the prompt below.
Review files and risks before approving any action.

Prompt to paste

Inspect the Agent Skill at https://github.com/potpie-ai/potpie/blob/HEAD/potpie/context-engine/adapters/inbound/cli/templates/agent_bundle/.agents/skills/potpie-change-timeline/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/potpie-change-timeline, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Potpie Change Timeline

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.

Fast Path

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

Apply Results

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.

Record History

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.

MCP Fallback

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.