メニュー
Designs pi extensions — new or refactoring — with full PRD, TypeScript best practices, anti-pattern audit, and migration plan. Use when creating, updating, or refactoring a pi extension.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Systematic dead code detection for pi extensions. Picks random extension, analyzes for unused exports, unreachable paths, dead branches, orphaned utilities, and other dead code patterns. Validates with proof, creates GitHub issue. Use before releases or when auditing extension quality.
Create a new GitHub release for cheasee-pi. Fetches all merged PRs since last tag, categorizes by title patterns, calculates version, runs checks (TypeScript + Go), syncs version strings, pushes tag for GoReleaser CI, updates release body. Use for any cheasee-pi release.
Creates GitHub issues on the internal repo. Reads repo + project config from .pi/settings.json, loads proper template, checks duplicates, files via gh CLI, adds to project board with status. Use for any internal issue.
Systematic bug hunting for pi extensions. Picks random extension, analyzes code using best-practice bug hunting techniques, validates findings with reproducible proof, creates GitHub issue with full report. Use when auditing extension quality or before releases.
Systematic detection of pi built-in API reimplementations in extensions. Picks random extension, cross-references custom code against LIVE pi documentation, finds where extensions reinvent built-in dialogs, file-queue, truncation, state management, rendering, bash execution, compaction, and more. Creates GitHub issues with migration steps and LOC reduction estimates. Use before releases or when auditing extension quality.
Renders the supervisor's chat messages with the REAL pi TUI — live theme proxy, Box, Markdown, actual ANSI render lines — so output is the bytes pi would draw, never hypothetical. Covers both synthetic fixtures (one per eventType) and full recorded-session workflow rendering (replay as-stored, convert old format to new eventType, or side-by-side diff). Use whenever you change `message-renderer.ts` or `handler.ts` event emission, or want to see, discuss, or iterate on what the supervisor's chat actually looks like. Triggers: "render supervisor", "supervisor render", "show supervisor output", "validate supervisor rendering", "supervisor workflow", "/supervisor-render".
| name | extension-spec |
| description | Designs pi extensions — new or refactoring — with full PRD, TypeScript best practices, anti-pattern audit, and migration plan. Use when creating, updating, or refactoring a pi extension. |
Design pi extensions following pi docs, TypeScript best practices, and anti-pattern audit.
No setup needed. All reference docs included.
read references/extension-spec.mdread /usr/lib/node_modules/@earendil-works/pi-coding-agent/docs/extensions.mdls /usr/lib/node_modules/@earendil-works/pi-coding-agent/examples/extensions/ls .pi/extensions/*.ts .pi/extensions/*/index.ts 2>/dev/nullSee references/extension-spec.md Mode Detection table.
| Input | Mode | Action |
|---|---|---|
refactor:<name> / update:<name> / fix:<name> | Refactor | Read existing extension, audit, produce PRD + migration |
$@ file in .pi/extensions/ | Refactor | Same — read, audit, produce PRD |
| Other / no arg | New | Analyze, research, design from scratch |
any types, no details: {}, no module-level mutable statepi.exec(), ctx.sessionManager, ctx.ui.*, pi.sendUserMessage(), ctx.cwd.pi/specs/<name>-prd.md$@ --implement: code after PRDSee full spec for: