compress-session
について
compress-sessionスキルは、会話履歴を構造化された要約に圧縮し、決定事項、構築されたツール、重要な進展といった、gitコミットでは捉えられない文脈を抽出します。このスキルは、ユーザーが明示的に圧縮を要求した場合、重要なマイルストーン達成後、あるいは長時間のセッションにおいて定期的に作動します。自動的に生成される要約はシーケンス番号で整理され、開発作業の「なぜ」と「どのように」を保持することに重点を置いています。
クイックインストール
Claude Code
推奨/plugin add https://github.com/majiayu000/claude-skill-registrygit clone https://github.com/majiayu000/claude-skill-registry.git ~/.claude/skills/compress-sessionこのコマンドをClaude Codeにコピー&ペーストしてスキルをインストールします
ドキュメント
Compress Session
Compress active session into structured summary. Capture decisions, tools built, breakthroughs - the "why" and "how" that git commits don't preserve.
When to Activate
- User says: "compress", "compress session"
- After significant milestones
- Every ~10 messages in long sessions
- Before ending major work
Process
1. Determine Sequence Number
ls -t inbox/session-summaries/$(date +%Y-%m-%d)*.md 2>/dev/null | head -1
- If files exist: increment (seq2, seq3...)
- If none: this is seq1
2. Review Conversation
Identify signal vs. noise:
- INCLUDE: Decisions, tools built, breakthroughs, key quotes, context
- SKIP: Pleasantries, process discussion without outcome, redundant info
3. Write Summary
Create: inbox/session-summaries/YYYY-MM-DD-HHMM-seqN.md
# Session Capture: YYYY-MM-DD [Sequence N]
**Time:** [Start] - [Current]
**Roles Active:** [List or "general"]
**Messages:** [Approximate range]
**Branch:** [git branch]
---
## Context
[1-3 sentence narrative of what happened this sequence]
---
## Decisions Made
- [Decision 1]
- Reason: [Why]
- [Decision 2]
---
## Tools/Workflows Built
- **[Name]:** [Description and purpose]
[Or: None this sequence]
---
## Breakthroughs/Insights
- [Insight] - [Significance]
---
## Key Quotes
- "[Quote]" ([Context])
---
## Files Created/Modified
[From git status]
- New: [files]
- Modified: [files]
---
## Next Steps
- [What's coming]
---
**Session compressed. Sequence [N] captured.**
4. Confirm
Session compressed. Sequence [N] captured.
Stored: inbox/session-summaries/YYYY-MM-DD-HHMM-seqN.md
What to Include
- Decisions affecting work/strategy/direction
- Tools/workflows built or planned
- Breakthroughs (creative, technical, conceptual)
- Context explaining why decisions were made
- Key quotes revealing intent
What to Skip
- Conversational filler
- Detailed implementation (git shows that)
- Process discussion without decision
- Speculation that didn't become action
Tone
- Concise, structured
- Bullet points over paragraphs
- Searchable and scannable
- Neutral observation
GitHub リポジトリ
関連スキル
content-collections
メタThis skill provides a production-tested setup for Content Collections, a TypeScript-first tool that transforms Markdown/MDX files into type-safe data collections with Zod validation. Use it when building blogs, documentation sites, or content-heavy Vite + React applications to ensure type safety and automatic content validation. It covers everything from Vite plugin configuration and MDX compilation to deployment optimization and schema validation.
creating-opencode-plugins
メタThis skill provides the structure and API specifications for creating OpenCode plugins that hook into 25+ event types like commands, files, and LSP operations. It offers implementation patterns for JavaScript/TypeScript modules that intercept and extend the AI assistant's lifecycle. Use it when you need to build event-driven plugins for monitoring, custom handling, or extending OpenCode's capabilities.
polymarket
メタThis skill enables developers to build applications with the Polymarket prediction markets platform, including API integration for trading and market data. It also provides real-time data streaming via WebSocket to monitor live trades and market activity. Use it for implementing trading strategies or creating tools that process live market updates.
cloudflare-turnstile
メタThis skill provides comprehensive guidance for implementing Cloudflare Turnstile as a CAPTCHA-alternative bot protection system. It covers integration for forms, login pages, API endpoints, and frameworks like React/Next.js/Hono, while handling invisible challenges that maintain user experience. Use it when migrating from reCAPTCHA, debugging error codes, or implementing token validation and E2E tests.
