pi-extensions

Merge or squash-merge a pull request and report best-effort remote and local source-branch cleanup. Use when user says "merge this PR", "squash merge", "md", "smd", or anything about merging pull requests.

(devtools plugin) Create a branch, commit changes, push, and open a PR — or just commit+push+PR if already on a feature branch. Links related issues from GitHub or Linear based on project tracker config.

Automate the release process. Use when user says "cut a release", "new version", "bump version", "publish release", or anything about versioning and publishing.

Plan, draft, and execute Exa deep-research workflows. Use when the user wants staged research planning, cost-aware discovery before deep synthesis, or an explicit deep-research report. Also use when the user asks to refine a research question, compare options, explore a market or technical landscape, gather sources cheaply before synthesis, or decide whether deep research is necessary.

Code context using Exa. Finds reliable code docs, snippets, API references, and debugging examples.

Company research using Exa search. Finds company context, competitors, and market signals.

Search financial reports using Exa. Finds SEC filings, earnings materials, and filings by company.

People research using Exa search. Finds experts, professional profiles, and public bios.

Search personal websites and blogs using Exa. Finds practitioner perspectives and independent analysis.

Search for research papers and academic content using Exa.

Create Architecture Decision Records in MADR 4.0 format for durable technical choices. Use whenever the user wants to create or record an ADR, compare technical options, evaluate trade-offs, decide between X and Y, document why a design choice was made, review a PRD or plan for ADR candidates, or capture a decision that will constrain future work even if they do not explicitly say 'ADR'.

Create implementation plans from PRDs by turning requirements into architecture, phases, dependencies, workstreams, and ADR candidates. Use whenever the user wants to plan how to build a PRD, break a PRD into implementation phases, sequence the work, identify components and risks, turn a spec into actionable engineering work, or decide what should happen first even if they do not explicitly ask for an 'implementation plan'.

Draft Product Requirements Documents for features, issues, and scoped work using a structured template with measurable goals, acceptance criteria, design decisions, and concrete file breakdowns. Use whenever the user asks to write a PRD, scope a feature, turn a GitHub or Linear issue into requirements, formalize a plan before implementation, break work into implementable requirements, or spec out what should be built even if they do not explicitly ask for a 'PRD'.

Explore and navigate Notion workspaces via MCP. Use when searching for pages, understanding database structure, finding content, creating or updating pages/databases, or managing Notion workspace content. Triggers when user asks about Notion, mentions Notion pages/databases, wants to find something in their wiki, update a page, add rows to a tracker, query a database, check meeting notes, or when the Notion MCP server is connected. Even if the user doesn't say 'Notion' explicitly — if they mention a wiki, knowledge base, or workspace page, this skill likely applies.

Guide the user through setting up Notion MCP with OAuth authentication