reflect

Analyzes recent OpenCode sessions to recommend reusable skills, agents, commands, and config changes.

Updated Jun 16, 2022
One-click install
npx skills add https://github.com/SimonZimmer/dotfiles --skill reflect-simonzimmer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reflect
Source: https://github.com/SimonZimmer/dotfiles/tree/main/.config/opencode/skills/reflect
Command: npx skills add https://github.com/SimonZimmer/dotfiles --skill reflect-simonzimmer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Repeated manual workflows and recurring friction across AI coding sessions often go unnoticed, so users keep re-explaining the same processes instead of turning them into reusable agent assets. ## Core Features & Use Cases - Workflow Pattern Detection: Reviews recent sessions, project notes, and existing agent assets to find repeated friction with frequency, confidence, and impact scoring. - Session Archaeology Mode: Queries the OpenCode SQLite database to analyze historical sessions across repos, caching per-session summaries and aggregating cross-repo patterns. - Smallest-Useful-Form Recommendations: Proposes prompt rules, skills, commands, custom agents, MCP permission changes, or playbooks, and asks for approval before changing any config. - Use Case: After noticing you repeatedly run the same release checks, run a reflection to get an evidence-backed proposal for a reusable command instead of re-typing the steps each time. ## Quick Start Ask the agent to run /reflect to review your recent work and suggest reusable improvements.

Frequently Asked Questions about reflect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze my OpenCode session history for repeated patterns?▼

Run /reflect --sessions to query the OpenCode SQLite database for recent sessions. Each session is summarized with goals, frictions, and recommendations, then aggregated across repos to rank recurring patterns by frequency and impact.

How do I turn a repeated workflow into a reusable skill or command?▼

Run /reflect with a focus area, and it inventories existing assets, scores the candidate on frequency, cost, risk, and stability, then proposes the smallest useful form such as a prompt rule, skill, or command before making any changes.

Does reflect change my OpenCode config automatically?▼

No. Reflect always presents a proposal and asks for approval before editing prompts, skills, commands, agents, MCP permissions, or config. When changes are applied, they take effect on the next OpenCode run or after a restart.

What happens when reflect finds no repeated workflows?▼

It reports that no strong repeated workflow was found and recommends creating nothing. Treating no-change as a valid outcome is part of its conservative, evidence-driven design.

When should I not use session reflection analysis?▼

Avoid it for one-off debugging, ordinary implementation work, broad architecture reviews, or speculative agent creation without workflow evidence. It is designed only for identifying repeated, stable patterns worth packaging.