Menu
Analyze pi session transcripts to discover patterns that could become AGENTS.md rules, skills, or prompt templates. Mines your usage history for automation opportunities.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Build PR-focused context packs (PR description + git diff + full changed files + related files via Scribe), then budget-fit and token-check with o200k-base.
Review a pull request for bugs, style issues, and guideline compliance. Local review - does not post to GitHub.
Build LLM-ready code dumps with optional docs, then count tokens with tokencount (o200k-base) against a context budget (for example 272k for GPT-5).
Compress images to a target file size using macOS sips. No dependencies required.
Multi-model code review. Runs code-review skill with 3 models in parallel, then synthesizes findings.
Compress videos to a target file size using ffmpeg two-pass encoding. Useful for Discord/Slack upload limits.
| name | session-analyzer |
| description | Analyze pi session transcripts to discover patterns that could become AGENTS.md rules, skills, or prompt templates. Mines your usage history for automation opportunities. |
Extracts and analyzes your pi session transcripts to find recurring patterns that could be automated.
# Extract transcripts for current directory
{baseDir}/analyze.js
# Extract transcripts for specific directory
{baseDir}/analyze.js /path/to/project
# Match multiple dirs by pattern (worktrees, variants, etc.)
{baseDir}/analyze.js --pattern orders-app
# Extract + analyze with subagents
{baseDir}/analyze.js --analyze
# Pattern + analyze (finds all matching session dirs)
{baseDir}/analyze.js --pattern orders-app --analyze
# Custom output directory
{baseDir}/analyze.js --output ./my-analysis --analyze
~/.pi/agent/sessions/
--pattern to match multiple directories (e.g., worktrees, feature branches)Without --analyze:
session-transcripts/
├── session-transcripts-000.txt
├── session-transcripts-001.txt
└── ...
With --analyze:
session-transcripts/
├── session-transcripts-000.txt
├── session-transcripts-000.summary.txt # Pattern analysis
├── session-transcripts-001.txt
├── session-transcripts-001.summary.txt
└── FINAL-SUMMARY.txt # Aggregated findings
Install dependencies (run once):
cd {baseDir}
npm install
Adapted from badlogic/pi-mono gist